Communication processing method and communications apparatus

ABSTRACT

Embodiments of this application provide a communication processing method. A data volume report reported by a terminal device includes a data volume on one of at least two paths in a radio bearer in a duplication mode, so that signaling overheads in a data volume reporting process of the terminal device can be reduced.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/714,650, filed on Dec. 13, 2019, which is a continuation ofInternational Application No. PCT/CN2018/091617, filed on Jun. 15, 2018,which claims priority to Chinese Patent Application No. 201710454166.4,filed on Jun. 15, 2017, and Chinese Patent Application No.201710682219.8, filed on Aug. 10, 2017. All of the afore-mentionedpatent applications are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

Embodiments of this application relate to the field of wirelesscommunications, and in particular, to a communication processing methodand a communications apparatus.

BACKGROUND

In a wireless communications system, a link in a direction from aterminal device to a radio access network is an uplink, and a link in adirection from the radio access network to the terminal device is adownlink. On the uplink and the downlink, the terminal device and theradio access device transmit various types of data, for example, controlsignaling or service data, based on various protocol layers developed bythe 3rd generation partnership project (3GPP) organization. Theseprotocol layers include a physical (PHY) layer, a media access control(MAC) layer, a radio link control (RLC) layer, a packet data convergenceprotocol (PDCP) layer, a radio resource control (RRC) layer, and thelike. Regardless of a layer at which data is transmitted, the data isfinally borne at the physical layer and transmitted in wireless space.

With the development of 5th generation mobile communicationstechnologies, some or all of data transmitted by a PDCP entity at thePDCP layer to an RLC entity at the RLC layer is duplicately transmittedon at least one other RLC entity corresponding to the PDCP entity. Thisprocessing manner is referred to as a duplication mode. In theduplication mode, a same piece of data may be duplicately transmitted inthe wireless space, thereby improving stability of data transmission.

However, how to manage various types of information in the duplicationmode to implement data transmission in the duplication mode is a problemthat urgently needs a solution.

SUMMARY

Embodiments of this application provide a communication processingmethod, to manage various types of information in a duplication mode.

A first aspect of the embodiments of the present application provides acommunication processing method, including the following content:

determining, by a terminal device, that a data volume report needs to betriggered for one of a first path and a second path that are in a radiobearer in a duplication mode, where in the duplication mode, PDCP dataon the radio bearer is transmitted on a first RLC entity correspondingto the first path, and is duplicately transmitted on a second RLC entitycorresponding to the second path;

triggering, by the terminal device, the data volume report, where thedata volume report indicates a data volume on the one path; and

sending, by the terminal device, the data volume report to a radioaccess network.

The technical solution provided in the first aspect is used to implementnotification management of a to-be-transmitted data volume of theterminal device in the duplication mode. The terminal device reports adata volume on one path in one radio bearer in the duplication mode,thereby avoiding signaling overheads caused by reporting data volumes onall paths.

Based on the first aspect, in a first possible implementation of thefirst aspect,

before the determining, by a terminal device, that a data volume reportneeds to be triggered for one path, the method further includes:

receiving, by the terminal device, a first message sent by the radioaccess network, where the first message indicates, to the terminaldevice, the one path for which the data volume report needs to betriggered.

Based on the first aspect, in a second possible implementation of thefirst aspect,

the determining, by a terminal device, that a data volume report needsto be triggered for one path includes:

selecting, by the terminal device, a path with a higher priority fromthe first path and the second path, as the one path for which the datavolume report needs to be triggered; or

selecting, by the terminal device based on a data volume, the one pathfor which the data volume report needs to be triggered, from the firstpath and the second path.

In the first possible implementation, the one path for which a datavolume needs to be notified by the terminal device is indicated by theradio access network. In the second possible implementation, theterminal device determines by itself the one path for which the datavolume needs to be notified. The first and the second possibleimplementations provide a plurality of implementation means fordetermining the one path for which the data volume needs to be notified.

Based on any one of the first aspect, or the first or the secondpossible implementation of the first aspect, in a third possibleimplementation of the first aspect, the method further includes:

receiving, by the terminal device, a second message sent by the radioaccess network, where the second message indicates a cell or a cellgroup corresponding to the first path and a cell or a cell groupcorresponding to the second path; and

the sending, by the terminal device, the data volume report to a radioaccess network includes:

sending, by the terminal device to the radio access network, the datavolume report in a cell or a cell group corresponding to the determinedone path.

In the third possible implementation, the radio access networkdesignates the cell or the cell group through which the data volume onthe one path determined by the terminal device is transmitted to theradio access network.

Based on the third possible implementation of the first aspect, in afourth possible implementation of the first aspect, the method furtherincludes:

receiving, by the terminal device, a second message sent by the radioaccess network, where the second message indicates a cell or a cellgroup corresponding to the first path and a cell or a cell groupcorresponding to the second path; and

the sending, by the terminal device, the data volume report to a radioaccess network includes:

sending, by the terminal device to the radio access network, the datavolume report in a cell or a cell group different from a cell or a cellgroup corresponding to the determined one path.

In the fourth possible implementation, when the cell corresponding tothe one path has no resource, it can still be ensured that the datavolume report of the one path is sent to the radio access network.

A second aspect of the embodiments of the present application provides acommunication processing method, including the following content:

receiving, by a terminal device, a first indication message sent by aradio access network, where the first indication message indicateswhether to activate a duplication mode of a radio bearer, and theduplication mode comprises some or all of data from a PDCP entity of theterminal device on a corresponding first RLC entity on a first path isduplicately transmitted on a corresponding second RLC entity on a secondpath; and

activating or deactivating, by the terminal device, the duplication modeof the radio bearer based on the first indication message.

According to the technical solution provided in the second aspect,activation of the duplication mode can be managed, and whether toactivate or deactivate the duplication mode is controlled by the radioaccess network.

Based on the second aspect, in a first possible implementation of thesecond aspect, the first indication message includes a first field and asecond field, the first field indicates that the first indicationmessage is a control message for the duplication mode, and the secondfield indicates whether to activate the duplication mode.

Based on the first possible implementation of the second aspect, in asecond possible implementation of the second aspect, the firstindication message further includes a third field, and the third fieldindicates the radio bearer corresponding to the duplication mode.

Based on the first possible implementation of the second aspect, in athird possible implementation of the second aspect, the second fieldindicates, via a bit state of one bit, whether to activate theduplication mode, and indicates, via a bit position of the one bit, theradio bearer corresponding to the duplication mode.

Based on the second aspect, in a fourth possible implementation of thesecond aspect, the first indication message includes a first field and asecond field, the first field indicates that the first indicationmessage is a control message for the duplication mode, and the secondfield indicates whether the first path is activated and whether thesecond path is activated; and if both the first path and the second pathare activated, the duplication mode is activated, or if at least one ofthe first path and the second path is deactivated, the duplication modeis deactivated or the first indication message is an invalid message.

Based on the fourth possible implementation of the second aspect, in afifth possible implementation of the second aspect, the first indicationmessage further includes a third field, and the third field indicates anidentifier of the first path and an identifier of the second path.

Based on the fourth implementation of the second aspect, in a sixthpossible implementation of the second aspect, the second field indicatesthe first path via a position of the first bit; indicates, via a bitstate of the first bit, whether the first path is activated; indicatesthe second path via a position of the second bit; and indicates, via abit state of the second bit, whether the second path is activated.

Based on the second aspect, in a seventh possible implementation of thesecond aspect, when the first path is activated, the first indicationmessage includes a first field and a second field, the first fieldindicates that the first indication message is a control message for theduplication mode, and the second field indicates whether the second pathis activated; and if the second path is activated, the duplication modeis activated, or if the second path is deactivated, the duplication modeis deactivated.

Based on the second aspect, in an eighth possible implementation of thesecond aspect, the first indication message includes a first field and asecond field, the first field indicates that the first indicationmessage is a control message for the duplication mode, and the secondfield indicates whether to activate the duplication mode; when the firstindication message is from a cell or a cell group corresponding to thefirst path, the second field specifically indicates whether the firstpath is activated, or when the first indication message is from a cellor a cell group corresponding to the second path, the second fieldspecifically indicates whether the second path is activated; and if boththe first path and the second path are activated, the duplication modeis activated, or if at least one of the first path and the second pathis deactivated, the duplication mode is deactivated.

In any one of the first to the eighth possible implementations of thesecond aspect, various message structure forms of the first indicationmessage used to indicate whether to activate the duplication mode areprovided. This is flexible and easy to implement.

Based on any one of the second aspect, or the first to the eighthpossible implementations of the second aspect, in a ninth possibleimplementation of the second aspect, the method further includes:triggering, by the terminal device, a data volume report indicating adata volume, where

when the duplication mode is activated, the data volume indicated in thedata volume report includes:

a data volume on one of the first path and the second path or a sum of adata volume on the first path and a data volume on the second path.

In the ninth possible implementation of the second aspect, the datavolume report may include data volumes on all paths, or may include adata volume on only one path. This increases flexibility of indicatingthe data volume in the data volume report.

Based on any one of the second aspect, or the first to the ninthpossible implementations of the second aspect, in a tenth possibleimplementation of the second aspect, the method further includes:

when the first indication message indicates that the duplication mode isactivated, determining, by the terminal device, whether there is data onat least one of the PDCP entity and the first RLC entity; and

if there is data on at least one of the PDCP entity and the first RLCentity, triggering, by the terminal device, the data volume report.

Based on the tenth possible implementation of the second aspect, in aneleventh possible implementation of the second aspect, the methodfurther includes:

if there is data on the PDCP entity, transmitting, by the terminaldevice, the data on the PDCP entity to the first RLC entity, andduplicating, to the second RLC entity, the data transmitted to the firstRLC entity.

Based on the tenth possible implementation of the second aspect, in atwelfth possible implementation of the second aspect, the method furtherincludes:

if there is data on the first RLC entity, duplicating, by the terminaldevice, some or all of the data on the first RLC entity to the secondRLC entity.

Based on the tenth possible implementation of the second aspect, in athirteenth possible implementation of the second aspect, the methodfurther includes:

if there is data on the first RLC entity, duplicating, by the terminaldevice, some or all of the data on the first RLC entity at a MAC layer,and indicating that the duplicated data is from the second path.

According to the technical solution in any one of the tenth and thetwelfth possible implementations of the second aspect, the data volumereport is triggered if there is to-be-transmitted data that has not beentransmitted, and transmission in the duplication mode is performed, sothat the radio access network can learn of a to-be-transmitted datavolume of the terminal device in a timely manner, and then provideservices of the data for the terminal device.

Based on any one of the second aspect, or the first to the twelfthpossible implementations of the second aspect, in a thirteenth possibleimplementation of the second aspect, when the first indication messageindicates that the duplication mode is activated, the duplicated data onthe first RLC entity and the second RLC entity has a same number.

Based on the thirteenth possible implementation of the second aspect, ina fourteenth possible implementation of the second aspect, the methodfurther includes:

sending, by the terminal device, a second indication message to theradio access network, where the second indication message includes astart number of the duplicated data on the second RLC entity in theduplication mode.

When the thirteenth or the fourteenth possible implementation of thesecond aspect is applied, the radio access network can correctly learnwhich data on each path is the duplicated data in the duplication mode.

Based on any one of the second aspect, or the first to the fourteenthpossible implementations of the second aspect, in a fifteenth possibleimplementation of the second aspect, when the first indication messageindicates that the duplication mode is activated, and the duplicateddata on the first RLC entity and the second RLC entity has differentnumbers, the method further includes:

notifying, by the terminal device, the radio access device of adifference between the difference numbers of the duplicated data.

When the fifteenth possible implementation of the second aspect isapplied, the radio access network can correctly learn which data on eachpath is the duplicated data in the duplication mode.

Based on any one of the second aspect, or the first to the fifteenthpossible implementations of the second aspect, in a sixteenth possibleimplementation of the second aspect, the method further includes:

receiving, by the terminal device, configuration information sent by theradio access network, where the configuration information indicates thecell or the cell group corresponding to the first path and the cell orthe cell group corresponding to the second path.

By applying the sixteenth possible implementation of the second aspect,the terminal device can learn of the cell or the cell groupcorresponding to each path, so as to send the duplicated data in thecorresponding cell or cell group under control of the radio accessnetwork.

Based on any one of the second aspect, or the first to the sixteenthpossible implementations of the second aspect, in a seventeenth possibleimplementation of the second aspect, the method further includes:triggering, by the terminal device, the data volume report indicatingthe data volume; and

when the first indication message indicates that the duplication mode isdeactivated, the data volume indicated in the data volume reportincludes: the data volume on the first path.

Based on the seventeenth possible implementation of the second aspect,in an eighteenth possible implementation of the second aspect, themethod further includes:

when the first indication message indicates that the duplication mode isdeactivated, determining, by the terminal device, whether there is dataon the second RLC entity; and

if there is data on the second RLC entity, triggering, by the terminaldevice, the data volume report, where the data volume indicated in thedata volume report further includes a data volume on the second RLCentity.

By applying the seventeenth and the eighteenth possible implementationsof the second aspect, although the duplication mode is deactivated, theterminal may still send non-duplicated data on the second RLC entity. Inthis case, the data volume report still includes the data on the secondRLC entity, so that the radio access network can accurately obtain theto-be-transmitted data volume of the terminal device in a timely mannerwhen the duplication mode is deactivated.

Based on any one of the second aspect, or the first to the eighteenthpossible implementations of the second aspect, in a nineteenth possibleimplementation of the second aspect, when the first indication messageindicates that the duplication mode is deactivated, the method furtherincludes at least one of the following:

determining, by the terminal device, not to duplicate, on the second RLCentity, the data on the PDCP entity that is transmitted to the first RLCentity;

discarding, by the terminal device, duplicated data on the second RLCentity;

discarding, by the terminal device, all duplicated data at the MAC layerthat is from the second RLC entity, or discarding duplicated data at theMAC layer that is from the second RLC entity and that is not stored intoa HARQ buffer;

determining, by the terminal device, duplicated data on the second RLCentity that does not need to be transmitted through an air interface,and if the determined duplicated data on the second RLC entity hasstarted to be transmitted through the air interface, continuing totransmit, by the transmit device, the determined duplicated data on thesecond RLC entity; or

transmitting, by the terminal device, data that is from the PDCP entityand that is not a duplicate of the data on the first RLC entity.

By applying the technical solution in the nineteenth possibleimplementation of the second aspect, when the duplication mode isdeactivated, the terminal can discard unnecessary duplicated data, so asto reduce a waste of resources.

Based on any one of the second aspect, or the first to the nineteenthpossible implementations of the second aspect, in a twentieth possibleimplementation of the second aspect, the method further includes:

when a quantity of retransmission times of the duplicated data on thesecond RLC entity reaches a maximum quantity of RLC retransmissiontimes, determining, by the terminal device, that a radio link failuredoes not be triggered, or triggering a radio link failure but noreestablishing a radio link.

According to the twentieth possible implementation of the second aspect,that a quantity of retransmission times of the duplicated data on thesecond RLC entity reaches a maximum quantity of RLC retransmission timesindicates network quality degradation. Because the first RLC entity canstill transmit data in the duplication mode, the terminal does not needto trigger the radio link failure, or does not reestablish the radiolink even if triggering the radio link failure. This can reduce aninterruption delay due to radio link reestablishment that is caused whenthe maximum quantity of retransmission times is reached.

A third aspect of the embodiments of this application provides acommunications apparatus. The communications apparatus includes aprocessing unit and a sending unit. The processing unit is configured toperform processing actions such as determining and triggering that areperformed by the terminal device in any one of the first aspect or thepossible implementations of the first aspect, and the sending unit isconfigured to perform sending actions of the terminal device in any oneof the first aspect or the possible implementations of the first aspect.The communications apparatus further includes a receiving unit,configured to perform receiving actions of the terminal device in anyone of the first aspect or the possible implementations of the firstaspect. Optionally, the communications apparatus is the terminal deviceor a part of the terminal device. Optionally, the processing unit may bea processor of the terminal device, the sending unit may be atransmitter of the terminal device, and the receiving unit is a receiverof the terminal device. Further, the terminal device may further includeanother electronic line, for example, a bus connecting the processor andthe transmitter, and a radio frequency antenna used for sending asignal. Optionally, the communications apparatus may alternatively be achip. The technical solution provided in the third aspect has thetechnical effects of the foregoing corresponding implementations. Fordetails, refer to the foregoing implementations.

A fourth aspect of the embodiments of this application provides acommunications apparatus. The communications apparatus includes aprocessing unit and a receiving unit. The processing unit is configuredto perform processing actions such as determining and triggering thatare performed by the terminal device in any one of the second aspect orthe possible implementations of the second aspect, and the receivingunit is configured to perform receiving actions of the terminal devicein any one of the second aspect or the possible implementations of thesecond aspect. The communications apparatus may further include asending unit, configured to perform sending actions of the terminaldevice in any one of the second aspect or the possible implementationsof the second aspect. Optionally, the communications apparatus is theterminal device or a part of the terminal device. Optionally, theprocessing unit may be a processor of the terminal device, the sendingunit may be a transmitter of the terminal device, and the receiving unitis a receiver of the terminal device. Further, the terminal device mayfurther include another electronic line, for example, a bus connectingthe processor and the transmitter, and a radio frequency antenna usedfor sending a signal. Optionally, the communications apparatus mayalternatively be a chip. The technical solution provided in the fourthaspect has the technical effects of the foregoing correspondingimplementations. For details, refer to the foregoing implementations.

A fifth aspect of the embodiments of this application provides acomputer storage medium. The computer storage medium includes programcode, and the program code is used to implement the technical solutionprovided in any one of the first aspect, the second aspect, or thepossible implementations thereof. The technical solution provided in thefifth aspect has the technical effects of the foregoing correspondingimplementations. For details, refer to the foregoing implementations.

A sixth aspect of the embodiments of this application provides acommunications apparatus. The communications apparatus includes aprocessor and a memory. The memory stores code, and the processorinvokes the code in the memory, so that all or some of the technicalsolutions provided in any one of the first aspect, the second aspect, orthe possible implementations thereof are implemented. The communicationsapparatus provided in the sixth aspect may be the terminal device in anyone of the foregoing aspects or the possible implementations thereof, ormay be a chip. When the communications apparatus is the chip, the chipincludes a processor including at least one gate circuit and a memoryincluding at least one gate circuit, each gate circuit includes at leastone transistor (for example, a field effect transistor) connectedthrough a conducting wire, and each transistor is made of asemiconductor material.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1A to FIG. 1H are schematic diagrams of a protocol stack of awireless communications system according to an embodiment of thisapplication;

FIG. 2 is a schematic flowchart of communication processing according toan embodiment of this application;

FIG. 3 is a schematic flowchart of communication processing according toan embodiment of this application;

FIG. 4 to FIG. 10 are schematic structural diagrams of a messageaccording to an embodiment of this application;

FIG. 11 to FIG. 13 are schematic diagrams of data transmission in aduplication mode according to an embodiment of this application;

FIG. 14 and FIG. 15 are schematic structural diagrams of acommunications apparatus according to an embodiment of this application;and

FIG. 16 is a schematic hardware structural diagram of a terminal deviceaccording to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

In a schematic architectural diagram of a protocol stack of a wirelesscommunications system shown in FIG. 1A, the wireless communicationssystem includes a terminal device and a radio access network.

The terminal device is also referred to as user equipment (UE) or amobile station, including a mobile phone, a handheld internet of thingsdevice, a wearable device, or the like.

The radio access network includes at least one radio access device, andeach radio access device includes an RRC layer, a PDCP layer, an RLClayer, a MAC layer, a PHY layer, and the like. A radio access device maybe a base station, a wireless local area network access point, or thelike. Base stations may be classified into two categories: macro basestations and small cells, and the small cells are classified into microbase stations, pico base stations, and the like. The wireless local areanetwork access point may be a router, a switch, or the like.

Based on protocol layers, the radio access network may be divided intoat least one distributed unit (DU) and one control unit (CU) connectedto the at least one distributed unit. Each of the at least onedistributed unit includes an RLC layer, a MAC layer, and a PHY layer.The control unit includes a PDCP layer, an RRC layer and a protocollayer above the RRC layer.

Data in the embodiments of this application includes signaling data andservice data. The service data includes enhanced mobile broadband (eMBB)data, massive machine type communications (mMTC) data, andultra-reliable and low latency communications (URLLC) data. In timedomain and frequency domain that are at a physical layer, a lengthoccupied by a transmission time unit in time and a width occupied by atransmission frequency unit in frequency may vary with differentwireless communication requirements of the service data. A size of thetransmission time unit and a size of the transmission frequency unitthat are used for data transmission may be defined in the wirelesscommunications system via different wireless parameter configurations.The wireless parameter configurations in a 5th generation mobilecommunications system may be referred to as numerology parameters or airinterface formats.

The foregoing data is transmitted between the terminal device and theradio access network by establishing at least one radio bearer (RB).Radio bearers are classified into two types: signaling radio bearersused to transmit the signaling data and data radio bearers used totransmit the service data. A radio bearer is a configuration of a set ofprotocol layer entities. A set of functional entities in one radiobearer includes one PDCP entity, at least two RLC entities correspondingto the PDCP entity, at least one MAC entity corresponding to the atleast two RLC entities, and at least one PHY entity corresponding to theat least one MAC entity.

In the architectural diagram of the wireless communications system shownin FIG. 1A, for one radio bearer between a transmit end and a receiveend, on the transmit end, one PDCP entity corresponds to at least twoRLC entities, and each of the RLC entities corresponds to one path forsending data. Correspondingly, on the receive end, one PDCP entitycorresponds to at least two RLC entities, and each of the RLC entitiescorresponds to one path for receiving data. Therefore, the radio bearerbetween the transmit end and the receive end includes at least twopaths.

As shown in FIG. 1A, the transmit end and the receive end each includeone PDCP entity, a first RLC entity corresponding to the one PDCPentity, and a second RLC entity corresponding to the one PDCP entity.The first RLC entity corresponds to a first path, and the second RLCentity corresponds to a second path. The transmit end sends data on thefirst path to the receive end in a cell 1 b or a cell group 1corresponding to the first path, and the receive end receives, in thecell 1 b or the cell group 1 corresponding to the first path, the dataon the first path that is sent by the transmit end. The transmit endsends data on the second path to the receive end in a cell 2 b or a cellgroup 2 corresponding to the second path, and the receive end receives,in the cell 2 b or the cell group 2 corresponding to the second path,the data on the second path. In a duplication mode, data from the onePDCP entity is duplicately transmitted on both the second RLC entity atthe transmit end and the first RLC entity at the transmit end, so thatstability of data sending by the transmit end can be improved.

Optionally, in a carrier aggregation scenario, the cell group 1 is amaster cell group, and the master cell group includes one primary celland at least one secondary cell, for example, a cell 1 a (the primarycell), the cell 1 b, and a cell 1 c; and the cell group 2 is a secondarycell group, and the secondary cell group includes at least one secondarycell, for example, a cell 2 a, the cell 2 b, and a cell 2 c. The mastercell group corresponds to the first RLC entity and the first path. Inthis case, the first RLC entity is also referred to as a primary RLCentity, and the second RLC entity is also referred to as a secondary RLCentity. The primary cell uses a primary carrier frequency, and thesecondary cell uses a secondary carrier frequency.

Optionally, in a carrier aggregation scenario, the cell group 1 is asecondary cell group, and the secondary cell group includes at least onesecondary cell, for example, a cell 1 a, the cell 1 b, and a cell 1 c;and the cell group 2 is a master cell group, and the master cell groupincludes one primary cell and at least one secondary cell, for example,a cell 2 a (the primary cell), the cell 2 b, and a cell 2 c. The mastercell group corresponds to the second RLC entity and the second path. Inthis case, the second RLC entity is referred to as a primary RLC entity,and the first RLC entity is referred to as a secondary RLC entity. Theprimary cell uses a primary carrier frequency, and the secondary celluses a secondary carrier frequency.

When the carrier aggregation scenario is an inter-radio access devicecarrier aggregation (also referred to as dual connectivity) scenario, aradio access device to which the master cell group belongs is a primaryradio access device, a radio access device to which the secondary cellgroup belongs is a secondary radio access device, and the terminaldevice is served by both the primary radio access device and thesecondary radio access device. Optionally, as shown in FIG. 1G, theterminal may use two MAC layer entities to separately establishconnections to the two radio access devices. During specificimplementation of this scenario, the PDCP entity and the first RLCentity corresponding to the PDCP entity are located on the primary radioaccess device, and the second RLC entity corresponding to the PDCPentity is located on the secondary radio access device; or the PDCPentity and the second RLC entity corresponding to the PDCP entity arelocated on the primary radio access device, and the first RLC entitycorresponding to the PDCP entity is located on the secondary radioaccess device.

Optionally, in this scenario, the one PDCP entity corresponds to onlyone primary RLC entity (the first RLC entity), and the PDCP entitycorresponds to at least one secondary RLC entity (at least one secondRLC entity).

Optionally, physical communications devices divided according to theschematic architectural diagram of the protocol stack of the wirelesscommunications system shown in FIG. 1A may be shown in FIG. 1B to FIG.1F, and FIG. 1G and FIG. 1H.

It should be noted that in a duplication mode on an uplink, the transmitend is the terminal device, and the receive end is the radio accessnetwork; and in a duplication mode on a downlink, the transmit end isthe radio access network, and the receive end is the terminal device.

The radio access network may separately configure the duplication modeon the uplink and the duplication mode on the downlink.

For example, the radio access network may separately configure cells orcell groups corresponding to all paths on the uplink and the downlink. Acell or a cell group corresponding to each path on the uplink may bedifferent from a cell or a cell group corresponding to each path on thedownlink.

Optionally, in the carrier aggregation scenario, a deactivation timer ofa secondary cell in a cell or a cell group corresponding to each path isdisabled when a duplication mode is activated, and is enabled when theduplication mode is deactivated (optionally, this may be indicated bythe radio access network). This manner can avoid a problem that datacannot be normally transmitted in the activated duplication mode becausethe secondary cell is disabled as the deactivation timer of thesecondary cell expires when the duplication mode is activated.

Optionally, in the carrier aggregation scenario, the radio accessnetwork may configure a radio bearer in the duplication mode. However,the configuration of the radio bearer does not include configuration ofa deactivation timer of each secondary cell in a secondary cell group(optionally, the configuration of the radio bearer does not includeconfiguration of a deactivation timer of each secondary cell in a mastercell group, either), to avoid a problem that data cannot be normallytransmitted in the activated duplication mode because the secondary cellis disabled as the deactivation timer of the secondary cell expires whenthe duplication mode is activated. If a secondary cell is not used forthe radio bearer in the duplication mode, the radio access network mayconfigure a deactivation timer of the secondary cell.

Optionally, in the carrier aggregation scenario, when configuring aradio bearer in the duplication mode, the radio access network mayconfigure a deactivation timer of a secondary cell in a cell or a cellgroup corresponding to each path, but there is data transmitted in thesecondary cell before the deactivation timer expires. For example, theradio access network configures specific data transmitted in thesecondary cell, and the specific data is transmitted in the secondarycell before the deactivation timer of the secondary cell expires, sothat expiration of the deactivation timer does not cause disabling ofthe secondary cell.

It should be noted that when RLC entities corresponding to one PDCPentity are separately located on different physical devices, in theduplication mode on the downlink, a communications device on which thePDCP entity is located may transmit only one piece of data to a physicaldevice on which one RLC entity is located, and physical devices on whichother RLC entities corresponding to the PDCP entity are locatedduplicate the piece of data to implement the duplication mode, that is,a communications system in which the PDCP entity is located does notneed to duplicate the piece of data and then send the data to each ofthe different physical devices on which the RLC entities correspondingto the PDCP entity are located. For example, in a schematicarchitectural diagram of the protocol stack of the wirelesscommunications system shown in FIG. 1C, an RLC entity 1 is located on anindependent DU1, and an RLC entity 2 is located on an independent DU2.One PDCP entity corresponding to the RLC entity 1 and the RLC entity 2is located on an independent CU. In this case, in the duplication modeon the downlink, the CU sends a piece of data to one of the DU1 and theDU2, and the other DU duplicates the piece of data sent by the CU. Thenboth the DU1 and the DU2 send the duplicated data to the terminaldevice.

As shown in FIG. 1H, an RLC entity 1 and an RLC entity 2 belong to oneDU, and a PDCP entity corresponding to the RLC entity 1 and the RLCentity 2 belongs to a CU. The CU determines a radio bearer correspondingto the PDCP entity when configuring a duplication mode, and notifies theDU of an identifier of the radio bearer corresponding to the RLC entity1 and the RLC entity 2 that correspond to the PDCP entity, and carriersor cell groups used for a first path and a second path on which the twoRLC entities are located.

In the scenario shown in FIG. 1H, the RLC entity 1 and the RLC entity 2belong to one DU, a transmission path is established between the DU andthe CU, the CU sends, on the transmission path, a piece of PDCP data tothe DU via the PDCP entity, and the DU duplicates, on a radio bearer onwhich the piece of PDCP data is located, the piece of PDCP data to theRLC entity 1 and the RLC entity 2 that correspond to the PDCP entity.Optionally, when sending the piece of PDCP data to the DU, the CU maynotify the DU of an identifier of the radio bearer on which the piece ofPDCP data is located, or at least one of identifiers of the RLC entity 1(the first path) and the RLC entity 2 (the second path) to which thepiece of PDCP data is to be sent. Further, the CU may further notify theDU of an internet protocol (IP) flow which the piece of PDCP databelongs to.

For a case in which the DU sends data to the CU, the DU determineswhether data on the two RLC entities in the radio bearer is duplicateddata in the duplication mode; and if yes, the DU sends a piece ofduplicated data to the CU on the transmission path between the DU andthe CU. For example, the DU may determine whether PDCP numberscorresponding to the data on the two RLC entities are the same, and ifthe PDCP numbers are the same, select data on one of the two RLCentities and send the data to the CU. If there is data with the samePDCP number on an RLC entity on the DU to be sent to the CU, the DUdiscards the data. For another example, the DU may determine whether RLCnumbers corresponding to the data on the two RLC entities are the same,and if the RLC numbers are the same, select data on one of the two RLCentities and send the data to the CU. If there is data with the same RLCnumber on an RLC entity on the DU to be sent to the CU, the DU discardsthe data.

In one radio bearer, because one RLC entity corresponds to one path inthe duplication mode, an identifier of the one RLC entity may be used toindicate the corresponding one path, or an identifier of the path may beused to indicate the corresponding one RLC entity. In some technicaldocuments, a path in a radio bearer is also referred to as a leg.

Optionally, different paths in one radio bearer are different logicalchannels, and use different logical channel identifiers, or identifiersof different RLC entities. In this case, the one radio bearercorresponds to at least two logical channels. The two logical channelsmay belong to a same logical channel group, or may belong to differentlogical channel groups.

Optionally, at least two paths in one radio bearer belong to a samelogical channel, and have a same logical channel identifier. Therefore,the one radio bearer corresponds to the same logical channel. In thiscase, to distinguish between different paths, the different paths mayhave a same logical channel identifier, but have different pathidentifiers.

When the radio bearer is a signaling radio bearer, regardless of whethera duplication mode is configured for the signaling radio bearer, a PDCPlayer in the signaling radio bearer sequentially processes PDCP data,for example, performs decryption and integrity check operations. Forexample, a PDCP layer of the signaling radio bearer at the receive endfirst receives a No. 2 packet when a No. 1 packet is not yet received.In this case, the PDCP layer needs to wait for arrival of the No. 1packet, and then process the No. 1 packet and the No. 2 packet.

In the embodiments of this application, duplication modes are separatelymanaged based on different radio bearers. For ease of description andunderstanding, in the embodiments of this application, duplication modemanagement of one radio bearer is used as an example. For a case ofanother radio bearer, refer to duplication mode management of the radiobearer. It should be noted that the radio bearer may be a signalingradio bearer or a data radio bearer.

Without loss of generality, one PDCP entity on one radio bearercorresponds to at least two RLC entities. Using any two RLC entitieshereafter: a first RLC entity and a second RLC entity, in the at leasttwo RLC entities as an example, paths on which the two RLC entities arelocated are a first path and a second path, respectively, and data onthe second RLC entity is a duplicate of some or all of data on the firstRLC entity.

It should be noted that, some or all of the data on the first RLC entitythat is duplicately transmitted on the second RLC entity is from the onePDCP entity. Optionally, the second RLC entity may not duplicatelytransmit data on the first RLC entity that is not from the PDCP entityand that is generated independently by the first RLC entity.

A first embodiment of this application provides a communicationprocessing method, and relates to management of notifying, by a terminaldevice in a duplication mode, a radio access network of ato-be-transmitted data volume. The first embodiment may be based on anarchitecture, of the protocol stack of the wireless communicationssystem, shown in any one of FIG. 1A, and FIG. 1B to FIG. 1F. A transmitend is the terminal device, and a receive end is the radio accessnetwork. Referring to a schematic flowchart of communication processingshown in FIG. 2, the first embodiment includes the following content.

200. The terminal device determines that a data volume report needs tobe triggered for one of a first path and a second path that are in aradio bearer in the duplication mode.

In a possible implementation, the terminal device receives a firstmessage sent by the radio access network, where the first messageindicates, to the terminal device, the one path for which the datavolume report needs to be triggered. For example, the first messagecarries an identifier of the one path. The identifier of the one pathmay be replaced with an identifier of an RLC entity corresponding to theone path.

In another possible implementation, the terminal device selects a pathwith a higher priority from the first path and the second path, as theone path for which the data volume report needs to be triggered.Optionally, a path on which each RLC entity corresponding to one PDCPentity is located is a logical channel, and a path priority is a logicalchannel priority.

In another possible implementation, the terminal device selects, basedon a data volume on each of the first path and the second path, the onepath for which the data volume report needs to be triggered. Although inthe duplication mode, a second RLC entity duplicates some or all of datatransmitted by the PDCP entity to a first RLC entity, each path has adifferent to-be-transmitted data volume within a current transmissiontime unit because each RLC entity has a different data processing speedor there is non-duplicated data on an RLC entity before the duplication.The terminal device may select a path having a smaller data volume, asthe one path for which the data volume report needs to be triggered, ormay select a path having a larger data volume, as the one path for whichthe data volume report needs to be triggered.

201. The terminal device triggers the data volume report, where the datavolume report indicates a data volume on the one path.

The data volume report may be a MAC layer message, for example, a bufferstatus report (BSR).

Optionally, when the first path and the second path belong to a samelogical channel, the terminal device triggers one data volume report,and notifies the data volume on the one path via the one data volumereport.

Optionally, when the first path and the second path are two differentlogical channels, respectively, and the two different logical channelsbelong to different logical channel groups, the terminal device triggerstwo data volume reports respectively corresponding to the two paths.Optionally, the terminal notifies the radio access network of the datavolume on the one path via the data volume report corresponding to theone path. Optionally, after sending the data volume report correspondingto the one path, the terminal does not cancel a data volume reportcorresponding to the other path.

Optionally, when the first path and the second path are two differentlogical channels, and the two different logical channels belong to asame logical channel group, the terminal device triggers one data volumereport, and notifies the data volume on the one path via the one datavolume report.

It should be noted that a data volume on the first path includes a datavolume on the one PDCP entity and a data volume on the first RLC entitywithin the current transmission time unit, and a data volume on thesecond path includes the data volume on the one PDCP entity and a datavolume on the second RLC entity within the current transmission timeunit.

In a possible implementation, there is an amount of data at a protocollayer above an RLC layer that has not been transmitted to an RLC entitywithin the current transmission time unit. In this case, each of thedata volume on the first path and the data volume on the second pathfurther include the amount of data that has not been transmitted to theRLC entity. For example, a service data adaptation protocol (SDAP) layeris further included above a PDCP protocol layer in a 5th generationmobile communications system. If there is a data volume on an SDAPentity corresponding to the PDCP entity within the current transmissiontime unit, each of the data volume on the first path and the data volumeon the second path further include the data volume on the SDAP entity.For another example, for a signaling radio bearer, an RRC layer isfurther included above the RLC protocol layer. If there is a data volumeon an RRC entity within the current transmission time unit, each of thedata volume on the first path and the data volume on the second pathfurther includes the data volume on the RRC entity.

In another possible implementation, the data volume report may not becapable of including data volumes on all paths having the data volumes.For example, a maximum quantity of paths for which data volumes may beindicated in the data volume report is set to N, but more than N pathshave data volumes; or after the terminal device has completely allocatedto-be-transmitted data, there is a remaining resource that canaccommodate a padding BSR, but the remaining resource cannot accommodatepadding BSRs and MAC subheaders that correspond to all of the pathshaving the data volumes. In this case, the terminal device determines,based on a priority of each path in respect of an air interface formatcorresponding to an uplink resource, paths for which data volumes may beindicated in the data volume report. For example, data volumes on N (1□N<M) paths with highest priorities in all of the paths or N logicalchannel groups including paths with highest priorities are selected.

In the duplication mode, one PDCP entity corresponds to two RLCentities, and the two RLC entities may correspond to two logicalchannels, respectively. The radio access network may set a priority ofone of the two logical channels to an infinitely low priority. In thisway, when there are sufficient uplink resources, data volumes on the twological channels may be reported in the data volume report; or whenthere are relatively strained or limited uplink resources, only abuffered data volume on a logical channel with a higher priority isreported.

Alternatively, priorities of the two logical channels may change, forexample, change based on a buffered data volume. When a data volume on alogical channel 1 is greater than a data volume on a logical channel 2,the logical channel 1 has a normal priority, and a priority of thelogical channel 2 is set to an infinitely low priority.

202. The terminal device sends the data volume report to the radioaccess network.

Optionally, before step 202, the method further includes:

receiving, by the terminal device, a second message sent by the radioaccess network, where the second message indicates a cell or a cellgroup corresponding to the first path and a cell or a cell groupcorresponding to the second path.

That the terminal device sends the data volume report to the radioaccess network specifically includes: The terminal sends the data volumereport to the radio access network in a cell or a cell groupcorresponding to the one path, or the terminal device sends the datavolume report to the radio access network in a cell or a cell groupdifferent from a cell or a cell group corresponding to the one path.

Optionally, when an RLC entity 1 on the first path and an RLC entity 2on the second path respectively belong to two radio access devices, theterminal device sends, in the cell or the cell group corresponding tothe one path, the data volume report to a radio access device to whichthe one path belongs.

Optionally, when an RLC entity 1 on the first path and an RLC entity 2on the second path belong to one radio access device, the terminaldevice sends, in the cell or the cell group corresponding to the onepath, the data volume report to the one radio access device.

Optionally, the terminal device determines whether there is a resource,for sending the data volume report, in the cell or the cell groupcorresponding to the one path. If there is no such resource in the cellor the cell group corresponding to the one path, the terminal devicesends the data volume report via a semi-persistent resource in anothercell or another cell group or a dynamic resource scheduled by the radioaccess network. Otherwise, the terminal sends the data volume report viathe resource in the cell or the cell group corresponding to the onepath.

Optionally, the semi-persistent resource in the another cell or theanother cell group is a resource that is allocated by the radio accessnetwork to the terminal device at a time and that may be used by theterminal device for a plurality of times, for example, a periodicresource reserved for the terminal device.

Further, the radio access network may determine data transmissionresources based on the data volume on the one path.

Because data on the second RLC entity is a duplicate of some or all ofdata transmitted from the PDCP entity to the first RLC entity, the radioaccess network may determine the data transmission resources in theradio bearer based on the data volume on the one path.

In a possible implementation, for one radio bearer, the radio accessnetwork multiplies the data volume on the one path by a quantity of allRLC entities corresponding to one PDCP entity in a duplication mode ofthe radio bearer, to learn of a to-be-transmitted data volume on theradio bearer. In this embodiment, the quantity of all the RLC entitiescorresponding to the one PDCP entity is 2. It should be noted that,because of complexity of a network environment, the data transmissionresources in the radio bearer that are determined by the radio accessnetwork are not necessarily sufficient to ensure that the terminaldevice can send all to-be-transmitted data on the radio bearer.

If the terminal device has a plurality of radio bearers, the radioaccess network determines data transmission resources in each radiobearer. Total data transmission resources available to the terminaldevice are a sum of determined data transmission resources in all of theradio bearers.

By applying the technical solution provided in the first embodiment, theterminal device notifies the radio access network of a data volume onone of at least two paths in the duplication mode. This can reducesignaling overheads caused by notifying, by the terminal device, datavolumes on all paths.

A second embodiment of this application provides a communicationprocessing method, and relates to activation management of a duplicationmode. The second embodiment may be based on an architecture, of theprotocol stack of the wireless communications system, shown in any oneof FIG. 1A, FIG. 1B to FIG. 1F, FIG. 1G and FIG. 1H. Optionally, becausethe second embodiment includes management of notifying, by a terminaldevice, a radio access network of a to-be-transmitted data volume whenthe duplication mode is activated, in activation management in thesecond embodiment, the first embodiment may be used as a possibleimplementation when a duplication mode on an uplink is activated.

Referring to a schematic flowchart of communication processing shown inFIG. 3, this embodiment of this application includes the followingcontent.

300. The radio access network determines whether to activate aduplication mode of a radio bearer.

Optionally, the radio access network may separately determine whether toactivate a duplication mode of the radio bearer on an uplink and aduplication mode of the radio bearer on a downlink.

Optionally, the radio access network measures channel quality of theuplink, and determines, based on the channel quality of the uplink,whether to activate the duplication mode of the radio bearer. If thechannel quality is lower than a preset threshold, the radio accessnetwork determines to activate the duplication mode of the radio beareron the uplink, so as to ensure stability of data transmission.Alternatively, if the terminal device has high-priority data to be senton the radio bearer, the radio access network determines to activate theduplication mode of the radio bearer. Optionally, when the channelquality of the uplink is higher than a preset threshold, particularlywhen channel quality of a primary cell or a master cell groupcorresponding to a first path in an uplink carrier aggregation scenariois quite high, the radio access network may not activate (that is,deactivate) the duplication mode of the radio bearer.

Optionally, in a scenario in which the radio access network includes aCU and a DU, the CU may determine whether to activate the duplicationmode, or the DU may determine whether to activate the duplication mode.

The CU or the DU may determine, based on cell load information or ameasurement report of the terminal device on cell signal quality,whether to activate the duplication mode.

For example, when serving cell signal quality reported by the terminaldevice via a measurement report is lower than a specific threshold (forexample, serving cell signal strength is lower than a specificthreshold, serving cell channel quality is lower than a specificthreshold, a ratio of HARQ negative acknowledgements exceeds a specificthreshold, or a quantity of RLC retransmission times exceeds a specificthreshold) or serving cell load is higher than a specific threshold, theCU or the DU determines that the duplication mode needs to be performed,so as to improve stability of data transmission. The CU or the DU mayactivate a duplication mode of at least one radio bearer of the terminaldevice, to improve stability of data transmission on the radio bearer.The CU or the DU further selects, based on signal quality of anothercell in the measurement report of the UE or cell load of another cell, acell in which data is duplicated on the radio bearer whose duplicationmode is activated, for example, selects a cell having good cell signalquality or low load.

The measurement report reported by the terminal device to the CU or theDU may be a reference signal received power (RSRP) or reference signalreceived quality (RSRQ) measurement report or an RLC/MAC/PHY layermeasurement report. The RSRP measurement or RSRQ measurement report isreported by the terminal device to the CU through an RRC layer; and theRLC/MAC/PHY layer measurement report may be a measurement report of theterminal device at a MAC layer that the CU requests the DU to send, forexample, to send periodically or on an event-triggered basis, to the CU.When requesting, from the DU, the measurement report of the terminal atthe RLC/MAC/PHY layer, the CU may notify the DU of which cell of whichterminal the requested MAC layer measurement report is specific to. TheCU may add, to a request, an identifier of a cell and a terminalidentifier of the terminal device on a CU-DU interface. In response tothe request of the CU, the DU sends the RLC/MAC/PHY layer measurementreport of the terminal to the CU periodically or on an event-triggeredbasis.

Optionally, when the radio bearer is a signaling radio bearer, the CUnotifies, via an RRC message, the DU of a signaling radio bearer whoseduplication mode is activated and paths that respectively correspond toat least two pieces of duplicated signaling on the signaling radiobearer. When the CU duplicates a PDCP data packet and sends the RRCmessage through the CU-DU interface, the CU indicates an SRB type and apath identifier (for example, a logical channel identifier) thatcorrespond to the RRC message, so that after obtaining the RRC message,the DU can transmit the RRC message to a path (or an RLC entity)corresponding to the path identifier in an SRB corresponding to the SRBtype. On the uplink, a duplication mode of one SRB is activated, and theSRB includes one PDCP entity in the CU. Therefore, when sending an RRCmessage to the CU through the CU-DU interface, the DU indicates an SRBtype corresponding to the RRC message, so that the CU learns of an SRBcorresponding to a PDCP entity to which the RRC message is transmitted.In this case, the path identifier may not be indicated.

For example, the CU generates an RRC message 1, and the RRC message 1 isborne on a signaling radio bearer 1. After a duplication mode of thesignaling radio bearer 1 is activated, the signaling radio bearer 1includes two paths: a path 1 and a path 2.

In a possible implementation, the CU duplicates the RRC message 1 toobtain two RRC messages 1; adds the first RRC message 1 to a CU-DUinterface message (for example, a first DL RRC transfer message) andindicates an SRB type and a path identifier 1 (e.g. a logical channelidentifier 1); and adds the second RRC message 1 to another CU-DUinterface message (for example, a second DL RRC transfer message) andindicates an SRB type and a path identifier 2 (e.g. a logical channelidentifier 2).

In another possible implementation, the CU may add the two duplicatedRRC messages 1 to one CU-DU interface message (for example, DL RRCtransfer), and provide a corresponding SRB type and path identifier foreach RRC message 1. Particularly, only one SRB type may be provided forRRC messages belonging to a same SRB, and the SRB type does not need tobe indicated for each RRC message.

According to this implementation, for at least two pieces of sameduplicated data, a plurality of pieces of same duplicated data aresequentially sent to at least two RLC entities corresponding to one PDCPentity.

In a possible example, a format in which one CU-DU interface message(for example, an F1 message) includes one downlink RRC transfer messageis described in the following table.

Information Information element type and element name reference (IE type(IE/Group name) Presence Range and reference) Semantics descriptionMessage type The message is mandatory. Terminal The message identifieron a is optional. CU-DU interface (DU- CU UE F1AP ID) Cell identifierThe message NCGI (new radio (Cell ID) is mandatory. cell globalidentifier) SRB type The message Bit string (BIT Each position in thebit is mandatory. STRING (3)) string represents one SRB type: the firstbit indicates an SRB1(S), the second bit indicates an SRB2(S), the thirdbit indicates an SRB3, and so on. Path identifier The message When aduplication is optional. mode is activated, a path identifier, forexample, a logical channel identifier, in the duplication mode isprovided. RRC container The message RRC message is mandatory.

The RRC container includes the RRC message. The SRB type is the SRB, theSRB1, the SRB2, the SRB1S, the SRB2S, or the SRB3 corresponding to theRRC message. During configuration, the CU notifies the DU that an SRB1of a terminal corresponds to a path identifier 1 and a path identifier2. In this case, when the CU subsequently sends the RRC message on theCU-DU interface (which may be referred to as an F1 interface for short),the path identifier 1 and the path identifier 2 that correspond to theRRC message are carried.

In another possible example, a format in which one CU-DU interfacemessage (for example, an F1 message) includes a plurality of downlinkRRC transfer messages is described in the following table.

Information Information element type and element name reference (IE type(IE/Group name) Presence Range and reference) Semantics descriptionMessage type The message is mandatory. Terminal The message identifieron a is optional. CU-DU interface (base station-CU UE F1AP ID) RRCmessage list Cell identifier The message NCGI (Cell ID) is mandatory.SRB type The message Bit string (BIT Each position in the bit ismandatory. STRING (3)) string represents one SRB type: the first bitindicates an SRB1(S), the second bit indicates an SRB2(S), the third bitindicates an SRB3, and so on. Path identifier The message When aduplication is optional. mode is activated, a path identifier, forexample, a logical channel identifier, in the duplication mode isprovided. RRC container The message RRC message is mandatory.

In an example, when the CU sends a duplicated PDCP data packet, anidentifier of a path to which the PDCP data packet is to be transmittedis carried in a packet header of the PDCP data packet. Alternatively, apath identifier is carried in a packet header of a CU-DU interfacemessage. For example, the interface message may be a user plane tunnel(e.g. GPRS tunneling protocol-user plane (GTP-U)) message.

In another example, the DU reads at least two received PDCP datapackets, and determines numbers of the at least two PDCP data packets.The DU further determines that PDCP data packets with same a number inthe at least two PDCP data packets are duplicated PDCP data on which aduplication mode is performed. The DU sends the determined duplicatedPDCP data to different RLC entities corresponding to one PDCP entity,for duplication.

Optionally, in a scenario in which the CU includes a CU control planeand a CU user plane, the CU user plane duplicates a PDCP data packet,and the CU control plane may determine, based on cell signal quality orcell load information, whether to activate a duplication mode of a radiobearer, and notify the CU user plane whether the duplication mode of theradio bearer is activated. When the CU control plane sends an RRCmessage through an F1 interface, and the CU user plane sends user planedata through the F1 interface, the method in the foregoing table is usedto indicate a path identifier corresponding to the RRC message or theuser plane data, so that the DU sends the RRC message or the user planedata to an RLC entity corresponding to an SRB or a DRB.

Optionally, in a scenario in which the CU includes a CU control planeand a CU user plane, the CU user plane duplicates a PDCP data packet,and the DU may determine, based on cell signal quality or cell loadinformation, whether to activate a duplication mode of a radio bearer,and notify the CU user plane whether the duplication mode of the radiobearer is activated. For specific details, refer to the foregoingmethod.

Optionally, the radio access network measures channel quality of thedownlink, and determines, based on the channel quality of the downlink,whether to activate the duplication mode of the radio bearer. If thechannel quality of the downlink is lower than a preset threshold, theradio access network determines to activate the duplication mode of theradio bearer on the downlink, so as to ensure stability of datatransmission. Alternatively, if the radio access network hashigh-priority data to be sent on the radio bearer, the radio accessnetwork determines to activate the duplication mode of the radio bearer.Optionally, when the channel quality of the downlink is higher than apreset threshold, particularly when channel quality of a primary cell ora master cell group corresponding to a first path is quite high in adownlink carrier aggregation scenario, the radio access network maydeactivate the duplication mode of the radio bearer on the downlink.

For duplication mode activation and deactivation, communicationprocessing performed on the uplink is similar to that on the downlink.In the following, on the uplink, a transmit end is the terminal device,and a receive end is the radio access network; and on the downlink, atransmit end is the radio access network.

Optionally, if the duplication mode is activated, the transmit end maytransmit data in the duplication mode. In this case, for one radiobearer, PDCP data on one PDCP entity in the radio bearer is transmittedto a corresponding first RLC entity on a first path, and is duplicatelytransmitted on a corresponding second RLC entity on a second path.

If the duplication mode is deactivated, the transmit end does not usethe duplication mode to transmit data. In this case, for one radiobearer, a second RLC entity does not duplicate some or all of data thatis on a first RLC entity. Optionally, to ensure that data can still betransmitted between the transmit end and the receive end when theduplication mode is deactivated, the radio access network may furtherinstruct one of the first RLC entity and the second RLC entity totransmit data from a PDCP entity when the duplication mode isdeactivated, and the other RLC entity no longer transmits any data fromthe PDCP entity, or the other RLC entity may transmit non-duplicateddata from the PDCP entity (in this case, the one of the first RLC entityand the second RLC entity that correspond to the one PDCP entity may notbe released, and there are still two paths for sending thenon-duplicated data). Optionally, when the duplication mode on theuplink is deactivated, the one RLC entity is determined by the radioaccess network that serves as the receive end, or is selected by theterminal device that serves as the transmit end. When the duplicationmode on the downlink is deactivated, the one RLC entity is determined bythe radio access network that serves as the transmit end. Optionally,the one RLC entity is a primary RLC entity.

Optionally, in a single-radio access device carrier aggregationscenario, if the duplication mode is deactivated, data is transmitted ona path on which one of the first RLC entity and the second RLC entity islocated, and the data is no longer transmitted on a path on which theother RLC entity is located. The duplication mode stops when a nexttransmission time unit after the transmit end confirms that theduplication mode is deactivated starts. If the transmit end is a radioaccess device, sending in the duplication mode stops when a nexttransmission time unit after the radio access device sends firstindication information indicating that the duplication mode isdeactivated starts. If the transmit end is the terminal device, sendingin the duplication mode stops when a next transmission time unit afterthe terminal device receives first indication information indicatingthat the duplication mode is deactivated starts. In this case, the PDCPentity at the transmit end sends PDCP data to one RLC entity, and nolonger sends duplicated PDCP data to another RLC entity, or sendsduplicated PDCP data to another RLC entity but the another RLC entitydoes not receive the sent duplicated PDCP data. If there isbefore-deactivation duplicated data (data that has not been transmittedthrough an air interface or to-be-retransmitted data (which has beentransmitted through an air interface but needs to be sent again)) in abuffer of the another RLC entity that has not been sent, the another RLCentity sends the before-deactivation duplicated data in the buffer, orthe another RLC entity discards the duplicated data in the buffer, orsends the to-be-retransmitted data in the duplicated data in the bufferbut discards the data that has not been transmitted through the airinterface. The another RLC entity may discard the data by performing RLCreestablishment, for example, by stopping an RLC timer corresponding tothe to-be-discarded data or by setting an RLC sending state variable ofthe to-be-discarded data to 0. According to this implementation, in thesingle-radio access device carrier aggregation scenario, if theduplication mode is deactivated, particularly when channel quality of apath becomes poor, duplicated data at an RLC layer is discarded, therebyreducing signaling overheads.

Optionally, in a dual connectivity scenario, if the duplication mode isdeactivated, on the downlink, a primary radio access device on which aprimary RLC entity is located and a secondary radio access device onwhich a secondary RLC entity is located do not send duplicated data tothe terminal device, but send non-duplicated data to the terminal.

Optionally, in a dual connectivity scenario, if the duplication mode isdeactivated, on the uplink, the terminal device sends non-duplicateddata to both a primary base station and a secondary base station, but nolonger sends duplicated data to the primary base station and thesecondary base station. Optionally, when the duplication mode of theradio bearer is deactivated, the terminal device may select a path froma first path and a second path in the radio bearer, as a deactivatedpath, or the radio access device determines a deactivated path from afirst path and a second path in the radio bearer. Optionally, thedeactivated path is disabled, or is prohibited from sending theduplicated data but can send the non-duplicated data. Optionally, if atransmit-end PDCP entity has sent the duplicated data to an RLC entitycorresponding to the deactivated path, the transmit-end RLC entitydiscards the duplicated data; or a transmit-end PDCP entity does nottransmit any data to a transmit-end RLC entity corresponding to thedeactivated path. Correspondingly, a receive-end RLC entitycorresponding to the deactivated path discards data from a MAC layer, ora receive-end MAC layer does not send any data to an RLC entitycorresponding to the deactivated path. For example, in a carrieraggregation scenario, if the first path corresponds to a primary cell ora master cell group, the second path is deactivated, and a second RLCentity on the second path no longer duplicates data transmitted on afirst RLC entity. If the second path corresponds to a primary cell or amaster cell group, the first path is deactivated, and a first RLC entityon the first path no longer duplicates data transmitted on a second RLCentity. In a possible implementation, in a dual connectivity scenario,both a primary radio access device and a secondary radio access deviceprovide communication services for the terminal device. For one radiobearer, two RLC entities corresponding to one PDCP entity arerespectively located on the primary radio access device and thesecondary radio access device. In a non-CU-DU networking scenario, thePDCP entity may be located on the primary radio access device, or may belocated on the secondary radio access device. In a CU-DU networkingscenario, the PDCP entity is located on a CU, and two DUs on which thetwo RLC entities corresponding to the PDCP entity are located are theprimary radio access device and the secondary radio access device.

In this possible implementation, when a duplication mode of the radiobearer is activated, duplicated data is transmitted on the primary radioaccess device and the secondary radio access device.

301. The radio access network sends a first indication message to theterminal device, where the first indication message is used to indicatewhether to activate the duplication mode of the radio bearer.

The first indication message may a MAC layer message or an RRC layermessage. Optionally, the radio access network may further notify aneffective time of the first indication message. The effective time isused to indicate when the duplication mode indicated in the firstindication message takes effect, or duration for which the duplicationmode is effective. In the CU-DU networking scenario, the firstindication message and the effective time may be notified by the CU tothe DU. For example, the DU sends, based on an indication of theeffective time, the MAC layer message to instruct the terminal toactivate the duplication mode. Alternatively, when the effective timeindicates the duration for which the duplication mode is effective, andthe DU may find, based on the duration, that the duplication mode is tobe ineffective, the DU instructs, via the MAC layer message, theterminal device to deactivate the duplication mode. The first indicationmessage and the effective message may be alternatively generated by theDU and sent to the CU. When the first indication message is generated bythe CU, the first indication message is sent by the CU to the DU, andthen the DU sends the first indication message to the terminal devicevia the MAC layer message. The effective time may be alternatively sentto the UE through the DU, so that the UE performs processing, forexample, makes the duplication mode effective at a specified time, andstops the duplication mode when the effective time is counted down to 0.

Optionally, the radio access device may further notify the terminaldevice that the first indication message is specific to the uplink orthe downlink.

Optionally, if the first indication message indicates that theduplication mode is deactivated, uplink duplicated data is no longertransmitted on at least two paths corresponding to one PDCP entity ofthe terminal device, but uplink non-duplicated data is sent on the atleast two paths. For example, the uplink non-duplicated data or a datavolume report indicating a data volume is sent on at least one path.Optionally, when the data volume is less than a threshold, the terminaldevice sends the uplink non-duplicated data on one of the at least onepath; or when the data volume is greater than or equal to a threshold,the terminal device sends the uplink non-duplicated data on all of theat least one path. Optionally, when the data volume is less than athreshold, the terminal device sends the data volume report on one ofthe at least one path; or when the data volume is greater than or equalto a threshold, the terminal device sends the data volume report on allof the at least one path. The one of the at least one path is indicatedby the radio access network, or is predefined in a protocol, forexample, predefined as the first path.

Optionally, in a dual connectivity scenario, if a radio access device (aprimary radio access device or a secondary radio access device) in theradio access network sends a first indication message to the terminaldevice, the radio access device that sends the first indication messagenotifies another radio access device whether the duplication mode isactivated or deactivated, so that when the duplication mode isdeactivated, the another radio access device reestablishes RLC.

Optionally, in a dual connectivity scenario, when the duplication modeis deactivated, the radio access network may configure which radioaccess device is used for continuing to transmit data on a path on whichthe radio access device is located, and the other radio access devicestops transmitting the duplicated data.

Optionally, in a dual connectivity scenario, if the terminal device andthe radio access network transmit, before the duplication mode isactivated, data to each other on a path on which a primary radio accessdevice is located, after the duplication mode switches from an activatedstate to a deactivated state, the terminal device and the radio accessnetwork transmit data to each other on the path on which the primaryradio access device is located (optionally, duplicated data in a HARQbuffer stops to be sent or is directly discarded after duplicated datathat is already in the HARQ buffer continues to be sent on a path onwhich a secondary radio access device is located). Similarly, if theterminal device and the radio access network transmit, before theduplication mode is activated, data to each other on a path on which asecondary radio access device is located, after the duplication modeswitches from an activated state to a deactivated state, the terminaldevice and the radio access network transmit data to each other on apath on which a primary radio access device is located (optionally,duplicated data in a HARQ buffer stops to be sent or is directlydiscarded after duplicated data that is already in the HARQ buffercontinues to be sent on a path on which a primary radio access device islocated).

To ensure that the terminal device can effectively receive the firstindication message, the first indication message may have one of thefollowing message structures.

In a possible implementation, in a schematic diagram of a messagestructure shown in FIG. 4, the first indication message includes a firstfield and a second field, the first field indicates that the firstindication message is a control message for the duplication mode, andthe second field indicates whether to activate the duplication mode. Thefirst field may be a set of binary bits including at least one bit, andthe second field may occupy one bit and indicate, via a bit state of theone bit, whether to activate the duplication mode. Optionally, the firstfield and the second field are included in a subheader of the MACmessage.

Optionally, in a schematic diagram of a message structure shown in FIG.5, the first indication message further includes a third field, and thethird field indicates the radio bearer corresponding to the duplicationmode. The third field may be specifically a radio bearer identifier. Ifonly one radio bearer in the duplication mode is configured for theterminal device, the first indication message does not need to includethe third field, and the terminal device can learn, without the thirdfield, whether the duplication mode of the radio bearer is activated. Ifat least two radio bearers are configured for the terminal device, theterminal device may learn, via the second field and the third field inthe first indication message, whether a duplication mode of each radiobearer is activated. Optionally, positions, corresponding to all theradio bearers, in the entire first indication message may be arrangedbased on values of identifiers of all the radio bearers.

Optionally, in a schematic diagram of a message structure shown in FIG.6, when at least two radio bearers are configured for the terminaldevice, a second field in the first indication message indicates, via abit position of a certain bit, a radio bearer corresponding to aduplication mode, and indicates, via a bit state of the bit, whether toactivate the duplication mode of the radio bearer. For example, aposition of the first bit in the second field indicates a radio bearer1, and a bit state of the first bit indicates whether a duplication modeof the radio bearer 1 is activated; and a position of the second bit inthe second field indicates a radio bearer 2, and a bit state of thesecond bit indicates whether a duplication mode of the radio bearer 2 isactivated. Optionally, positions, corresponding to all the radiobearers, in the entire first indication message may be arranged based onvalues of identifiers of all the radio bearers.

Optionally, in FIG. 6, a quantity of bits in the second field in thefirst indication message is a preset value, for example, a maximumquantity of identifiers of radio bearers or a maximum quantity of radiobearers that can be supported by the terminal device. Each radio bearercorresponds to one bit position, and the radio bearers may be arrangedin ascending order or descending order of the values of the identifiersof the radio bearers. Some radio bearers may support the duplicationmode (therefore, there is a case of whether the duplication mode isactivated), and some radio bearers may not support the duplication mode.Optionally, the quantity of bits in the second field is a multiple of 8,for example, 32 bits, so that a message format is in a unit of anintegral multiple of bytes. For example, if the terminal device cansupport a maximum of 32 radio bearers, the quantity of bits in thesecond field is 32, and each radio bearer corresponds to one bitposition. In an actual communication process, two of the 32 radiobearers configured for the terminal device support the duplication mode,for example, the radio bearer 1 and the radio bearer 2. When receivingthe first indication message, the terminal device detects states of bitsin corresponding bit positions on the radio bearer 1 and the radiobearer 2, and thereby can learn whether the duplication mode of theradio bearer 1 and the duplication mode of the radio bearer 2 areactivated. Because a radio bearer 3 to a radio bearer 32 are notconfigured for the terminal device or may not support a duplication modeduring actual communication, the terminal device ignores states, in thefirst indication message, of bits in bit positions corresponding to theradio bearer 3 to the radio bearer 32.

Optionally, assuming that X radio bearers (for example, radio bearers 1,3, and 5) are configured for the terminal device, the radio accessnetwork sets, based on an identifier value of a radio bearer, that bitstates of the first X bits or the last X bits in the second field in thefirst indication message correspond to whether duplication modes of theX radio bearers are activated (for example, the first bit corresponds tothe radio bearer 1, the second bit corresponds to the radio bearer 3,and the third bit corresponds to the radio bearer 5), and the terminaldevice reads the first X bits or the last X bits in the second field inthe first indication message to learn whether the duplication modes ofthe X radio bearers are activated, and ignores other bits included inthe second field.

Optionally, at least two radio access devices in the radio accessnetwork provide communication services for the terminal device byestablishing a plurality of radio bearers (for example, in the dualconnectivity scenario). Some radio bearers span radio access devices(for example, in one radio bearer, a PDCP entity and a first RLC entityare located on a radio access device A, and a second RLC entity islocated on a radio access device B), and some radio bearers do not spanthe radio access devices (for example, in one radio bearer, a PDCPentity, a first RLC entity, and a second RLC entity are all located on aradio access device A). In this case, a radio access device knows radiobearers established on the radio access device, but does not know radiobearers on other radio access devices serving a same terminal.

In an implementation, each radio access device sends a first indicationmessage to the terminal device, and each first indication messageindicates whether a duplication mode of a radio bearer on each radioaccess device is activated. For example, a first indication message sentby a radio access device A indicates whether a duplication mode of atleast one radio bearer on the radio access device A is activated, and afirst indication message sent by a radio access device B indicateswhether a duplication mode of at least one radio bearer on the radioaccess device B is activated. The radio access device A arranges allradio bearers on the radio access device A based on identifier values(1, 3, and 5), and sets bit states of the first X bits or the last Xbits in a second field based on the identifier values of the radiobearers on the radio access device A. The radio access device B arrangesall radio bearers on the radio access device B based on identifiervalues (2, 4, and 5), and sets bit states of the first X bits or thelast X bits in a second field based on the identifier values of theradio bearers on the radio access device B.

In another implementation, these radio access devices may make, throughnotification and negotiation, positions of all bits in a second field inone first indication message correspond to all radio bearers, and oneradio access device sends the first indication message to the terminaldevice. In this case, the first indication message indicates whetherduplication modes of the radio bearers on all of the radio accessdevices are activated. For example, radio bearers on the radio accessdevice A may be placed on the first several bits in the second field inthe first indication message, and positions of bits corresponding to theradio bearers are arranged among the first several bits based onidentifier values of the radio bearers on the radio access device A; andradio bearers on the radio access device B may be placed on the lastseveral bits in the second field, and positions of bits corresponding tothe radio bearers are arranged among the last several bits based onidentifier values of the radio bearers on the radio access device B. Foranother example, all radio bearers that can be supported by the terminaldevice may be arranged in the first indication message based onidentifier values; the radio access network sets, based on theidentifier values of all the radio bearers, that bit states of the firstX (an integer greater than or equal to 1) bits or the last X bits in thesecond field in the first indication message correspond to whetherduplication modes of the X radio bearers currently configured for theterminal are activated; and one radio access device sends the firstindication message to the terminal device. In this case, the firstindication message indicates whether the duplication modes of thecurrently configured radio bearers are activated.

Optionally, the radio access network may notify the terminal device of acorrespondence between a bit position in the second field in the firstindication message and a radio bearer, so that the terminal learns acertain bit corresponds to a radio bearer. The terminal detects a stateof a bit whose bit position corresponds to a radio bearer configured forcommunication, to learn whether a duplication mode of the configuredradio bearer is activated. In another possible implementation, in aschematic diagram of a message structure shown in FIG. 7, the firstindication message includes a first field and a second field, the firstfield indicates that the first indication message is a control messagefor the duplication mode, and the second field indicates whether thefirst path and the second path are activated. Optionally, the secondfield includes two bits: One bit indicates whether the first path isactivated, and the other bit indicates whether the second path isactivated. When both the first path and the second path are activated,the duplication mode is activated. When at least one of the first pathand the second path is deactivated, the duplication mode is deactivated,or the first indication message is an invalid message. If the firstindication message is the invalid message, the terminal device discardsthe first indication message. Optionally, the first indication messagemay include a third field, and the third field indicates identifiers ofthe first path and the second path or an identifier of a radio bearer inthe duplication mode. Optionally, positions, corresponding to all paths,in the entire first indication message may be arranged based onidentifier values of all the paths.

Optionally, in a diagram of a message structure shown in FIG. 8, asecond field in the first indication message indicates the first pathvia a position of the first bit, and indicates, via a bit state of thefirst bit, whether the first path is activated; and indicates the secondpath via a position of the second bit, and indicates, via a bit state ofthe second bit, whether the second path is activated. In this manner,one bit can not only indicate one path but also indicate whether thepath is activated. Optionally, positions, corresponding to all paths, inthe entire first indication message may be arranged based on identifiervalues of all the paths.

In another possible implementation, assuming that the first path isalways activated, the first indication message may indicate whether thesecond path is activated, so as to indicate whether a duplication modeof a radio bearer is activated. In a diagram of a message structureshown in FIG. 9, the first indication message includes a first field anda second field, the first field indicates that the first indicationmessage is a control message for the duplication mode, and the secondfield indicates whether the second path is activated. In this case, whenthe second path is activated, the duplication mode is activated, or whenthe second path is deactivated, the duplication mode is deactivated.Optionally, the first indication message further includes a third field,and the third field indicates an identifier of the second path.Optionally, in this possible implementation, the cell or the cell groupcorresponding to the first path is a primary cell or a master cellgroup, or a path identifier of the first path is less than a pathidentifier of the second path.

Optionally, in a diagram of a message structure shown in FIG. 10, asecond field in the first indication message indicates the second pathvia a position of the first bit, and indicates, via a bit state of thefirst bit, whether the second path is activated; and indicates thesecond path via a position of the second bit, and indicates, via a bitstate of the second bit, whether the second path is activated. In thismanner, one bit can not only indicate one path but also indicate whetherthe path is activated. Optionally, positions, corresponding to allpaths, in the entire first indication message may be arranged based onidentifier values of all the paths.

In another possible implementation, the first indication messageincludes a first field and a second field, the first field indicatesthat the first indication message is a control message for theduplication mode, and the second field indicates whether the duplicationmode is activated. If the first indication message is from the cell orthe cell group corresponding to the first path, the second fieldcontrols whether the first path is activated; or if the first indicationmessage is from the cell or the cell group corresponding to the secondpath, the second field controls whether the second path is activated.When both the first path and the second path are activated, theduplication mode is activated. When one of the first path and the secondpath is deactivated, the duplication mode is deactivated. Optionally,positions, corresponding to all paths, in the entire first indicationmessage may be arranged based on identifier values of all the paths.

If the cells or the cell groups corresponding to the first path and thesecond path belong to one DU in the radio access network, in step 301,the DU or a CU corresponding to the DU generates the first indicationmessage, and the DU sends the first indication message, to indicatewhether the duplication mode is activated.

If the cells or the cell groups corresponding to the first path and thesecond path belong to two different DUs corresponding to one CU in theradio access network, in step 301, the two different DUs mayrespectively indicate, via the cells or the cell groups corresponding tothe first path and the second path, whether the first path and thesecond path are activated, via the first indication message.Alternatively, in a dual connectivity scenario of carrier aggregation,one of the two different DUs indicates, via the first indicationmessage, whether the first path and the second path are activated.Optionally, the first indication message may be control plane signalingor user plane indication information. The user plane indicationinformation and the duplicated data may be sent simultaneously.

If the cells or the cell groups corresponding to the first path and thesecond path belong to two different DUs corresponding to different CUsin the radio access network, in step 301, the two different DUs mayrespectively indicate, via the first indication message and via thecells or the cell groups corresponding to the first path and the secondpath, whether the first path and the second path are activated.Alternatively, in a dual connectivity scenario of carrier aggregation,one of the two different DUs indicates, via the first indicationmessage, whether the first path and the second path are activated.

If the radio access network is not divided into a CU and a DU based onprotocol layers, and the cells or the cell groups corresponding to thefirst path and the second path belong to two different radio accessdevices in the radio access network, in step 301, the two differentradio access devices may respectively indicate, via the first indicationmessage and via the cells or the cell groups corresponding to the firstpath and the second path, whether the first path and the second path areactivated. Alternatively, in a dual connectivity scenario of carrieraggregation, one of the two different radio access devices indicates,via the first indication message, whether the first path and the secondpath are activated.

According to the technical solution provided in step 300 and step 301,the terminal device can learn whether a duplication mode of a radiobearer on at least one of the uplink and the downlink is activated.

Based on the technical solution provided in step 300 and step 301, forthe downlink or the uplink, regardless of whether the duplication modeis activated, one of all paths corresponding to one PDCP entity at thetransmit end meets a trigger condition of a radio link failure, but atleast one path can still be used to transmit data. In this case, thetransmit end determines that there is no need to trigger the radio linkfailure of the path, or even if the radio link failure of the path istriggered, the transmit end does not reestablish a radio link to thereceive end on the path. Optionally, when all paths corresponding to onePDCP entity meet a trigger condition of a radio link failure, thetransmit end triggers the radio link failure. Optionally, for theuplink, the terminal device serving as the transmit end notifies theradio access network that the radio link failure occurs. Particularly,when the radio bearer is a signaling radio bearer, radio linkreestablishment is triggered only when the radio link failure isdetected on all of the paths corresponding to the one PDCP entity in thesignaling radio bearer; otherwise, the radio link failure is nottriggered.

Based on the technical solution provided in step 300 and step 301, forthe downlink or the uplink, in a carrier aggregation scenario,regardless of whether the duplication mode is activated, a radio linkfailure can be triggered for a path on which a primary RLC entity at thetransmit end is located, and a radio link failure cannot be triggeredfor a path on which a secondary RLC entity at the transmit end islocated. For example, a maximum quantity of RLC retransmission timesthat is set by the secondary RLC entity is set to an infinite value, ora quantity of RLC retransmission times is not counted. Alternatively,even if a radio link failure can be triggered for a path on which asecondary RLC entity is located, radio link reestablishment is notperformed.

When a quantity of retransmission times of the duplicated data on thesecond RLC entity reaches the maximum quantity of RLC retransmissiontimes, communication quality cannot be ensured in the cell or the cellgroup corresponding to the second path. However, the first path on whichthe first RLC entity is located can still transmit data. This can ensurecontinuous data transmission, and avoid a data interruption problemcaused by radio link reestablishment.

Optionally, for the uplink or the downlink, when the duplication mode isdeactivated, the foregoing method further includes at least one of thefollowing:

determining, by the transmit end, not to duplicate, on the second RLCentity, the data on the PDCP entity that is transmitted to the first RLCentity;

discarding, by the transmit end, duplicated data on the second RLCentity;

discarding, by the transmit end, all duplicated data at a MAC layer thatis from the second RLC entity, or discarding duplicated data at a MAClayer that is from the second RLC entity and that is not stored into aHARQ buffer;

determining, by the transmit end, duplicated data on the second RLCentity that does not need to be transmitted through an air interface,and if the determined duplicated data on the second RLC entity hasstarted to be transmitted through the air interface, continuing totransmit, by the transmit end, the determined duplicated data on thesecond RLC entity; and

transmitting, by the transmit end, data that is from the PDCP entity andthat is not a duplicate of the data on the first RLC entity.

Optionally, when the duplication mode is deactivated, if the second RLCentity no longer sends any data, the transmit end may further release aresource occupied by the second RLC entity.

In an extended possible implementation, when the duplication modeswitches from the deactivated state to the activated state, the methodfurther includes at least one of the following possible implementations.

If there is data on a transmit-end PDCP entity, the transmit endtransmits the data on the PDCP entity to the first RLC entity, andduplicates, onto the second RLC entity, the data transmitted to thefirst RLC entity. In a schematic diagram of data transmission shown inFIG. 11, before the duplication mode is activated, data 37 and data 38on the PDCP entity are to be transmitted, data 35 and data 36 on thefirst RLC entity are to be transmitted, and there is no data on thesecond RLC entity. After the duplication mode is activated, the transmitend transmits the data 37 and the data 38 on the PDCP entity to thefirst RLC entity, and duplicates the data 37 and the data 38 onto thesecond RLC entity.

If there is data on the first RLC entity, the terminal device duplicatessome or all of the data on the first RLC entity onto the second RLCentity. A part of data that is already on the first RLC entity before acurrent transmission time unit may not be duplicately transmitted ontothe second RLC entity. In a schematic diagram of data transmission shownin FIG. 12, before the duplication mode is activated, data 35 and data36 on the first RLC entity are to be transmitted. After the duplicationmode is activated, the data 35 and the data 36 on the first RLC entityare duplicately transmitted onto the second RLC entity.

If there is data on the first RLC entity, the terminal device transmitssome or all of the data on the first RLC entity to a MAC layer,duplicates the data at the MAC layer, and indicates that the duplicateddata is from a second path. In other words, although the duplicated datais not from the second RLC entity, the MAC layer still indicates thatthe duplicated data is from the second RLC entity on the second path. Inthis case, when the data is duplicated at the MAC layer, indicating thatthe duplicated data is from the second RLC entity is equivalent to thatthe second RLC entity duplicates some or all of the data that is on thefirst RLC entity. In a schematic diagram of data transmission shown inFIG. 13, before a duplication mode is activated, data 35 and data 36 onthe first RLC entity have been transmitted to the MAC layer, and thesecond RLC entity does not duplicate the data 35 and the data 36; andafter the duplication mode is activated, the MAC layer duplicates thedata 35 and the data 36, and indicates that the duplicated data 35 andthe duplicated data 36 are from a second path, that is, are transmittedfrom the second RLC entity on the second path. The MAC layer sends thedata 35 and the data 36 from the first RLC entity to a primary cell or amaster cell group corresponding to a first path, and sends theduplicated data 35 and the duplicated data 36 to a secondary cell or asecondary cell group corresponding to the second path.

In an extended possible implementation, particularly for duplicationmode management on the uplink, the transmit end is the terminal device,and the receive end is the radio access network. The method furtherincludes the following content.

In an implementation, 302′. If the first indication message indicatesthat the duplication mode is deactivated, the terminal device cancels adata volume report that has been triggered for the second path.Optionally, the terminal device is configured by the radio accessnetwork to cancel, upon receiving the first indication messageindicating that the duplication mode is deactivated, the data volumereport that has been triggered for the second path.

In an alternative implementation of step 302′, 302. The terminal devicetriggers the data volume report based on the first indication message.

The data volume report may be the MAC layer message, for example, a BSR.

When the first indication message indicates that the duplication mode ofthe radio bearer is activated, a data volume indicated in the datavolume report may include data volumes on the first path and the secondpath, or may include a data volume on one of the first path and thesecond path, as described in step 201 in the foregoing methodembodiment.

Optionally, when the data volume indicated in the data volume reportincludes the data volumes on the first path and the second path, a datavolume on one of the first path and the second path may be 0. If thereis a resource in the cell or the cell group corresponding to the firstpath, the data volume report is sent in the cell or the cell groupcorresponding to the first path. If there is a resource in the cell orthe cell group corresponding to the second path, the data volume reportis also sent in the cell or the cell group corresponding to the secondpath. Optionally, after the data volume report is sent on both the firstpath and the second path, the terminal device cancels the data volumereport. If a resource in the second path is used to send the data volumereport. If there is no resource in the cell or the cell groupcorresponding to the one path, the terminal device sends the data volumereport via a semi-persistent resource in another cell or another cellgroup. Otherwise, the terminal sends the data volume report via theresource in the cell or the cell group corresponding to the one path.

When the first indication message indicates that a duplication mode of aradio bearer is deactivated, a second RLC entity on a second path in theradio bearer does not perform duplication. In this case, the data volumeindicated in the data volume report includes a data volume on a firstpath in the radio bearer.

When the duplication mode of the radio bearer is deactivated, duplicateddata is no longer transmitted on the second path, but data that is fromthe PDCP entity and that is not a duplicate of the data on the first RLCentity may be transmitted on the second path. In this case, when theterminal device determines that there is still to-be-sent data on thesecond RLC entity, the data volume indicated in the data volume reportfurther includes a data volume of the non-duplicated data on the secondpath.

When the duplication mode of the radio bearer is activated, same data onthe radio bearer may be transmitted on both the first path and thesecond path respectively corresponding to the first RLC entity and thesecond RLC entity in the radio bearer, so as to improve stability ofdata transmission. When the duplication mode of the radio bearer isdeactivated, the second path in the radio bearer transmits data (thatis, non-duplicated data) different from the data on the first RLCentity, so as to improve efficiency of data transmission. Certainly,when the duplication mode of the radio bearer is deactivated, the secondpath in the radio bearer may alternatively no longer transmit any data,until the first indication message sent by the radio access networkindicates that the duplication mode is activated.

In a possible implementation, the terminal device triggers the datavolume report immediately after receiving the first indication message(regardless of an indication of whether the duplication mode isactivated in the first indication message). Optionally, the terminaldevice is configured by the radio access network to trigger the datavolume report immediately after receiving the first indication message.

In a possible implementation, when the first indication messageindicates that the duplication mode is activated, the terminal devicefurther determines whether there is data on at least one of the PDCPentity and the first RLC entity, and if yes, the terminal devicetriggers the data volume report.

Optionally, based on step 302, the method in the second embodimentfurther includes the following steps.

303. The terminal device sends the data volume report to the radioaccess network when there is a resource for sending the data volumereport.

304. The radio access network allocates data transmission resources tothe terminal device based on the data volume indicated in the datavolume report.

305. The terminal device sends data to the radio access network based onthe data transmission resources.

In step 304 and step 305, the radio access network may indicate, in theallocated data transmission resources, a resource allocated to the cellor the cell group corresponding to the first path and a resourceallocated to the cell or the cell group corresponding to the secondpath.

306. The radio access network receives, on the data transmissionresources, the data sent by the terminal device.

In step 306, if receiving the data from the cell or the cell groupcorresponding to the first path, the radio access network delivers thereceived data to the first RLC entity in the radio access network forprocessing; or if receiving the data from the cell or the cell groupcorresponding to the second path, the radio access network delivers thereceived data to the second RLC entity in the radio access network forprocessing. The first RLC entity and the second RLC entity converge theprocessed data on one PDCP entity.

According to the technical solution provided in the second embodiment,the transmit end and the receive end may perform communicationprocessing based on a status of whether the duplication modes on theuplink and the downlink are activated, so as to implement managementwhen the duplication modes on the uplink and the downlink are activatedor deactivated.

A third embodiment of this application provides a communicationprocessing method, and the third embodiment relates to a configurationmanagement method for a duplication mode on an uplink or a downlink.Optionally, this method may be combined with the solution in the secondembodiment, and the configuration management method provided in thethird embodiment is applied before the activation management method inthe second embodiment. The third embodiment may be based on thearchitecture, of the protocol stack of the wireless communicationssystem, shown in any one of FIG. 1A, and FIG. 1B to FIG. 1F.

Referring to a schematic flowchart of the communication processingmethod shown in FIG. 4, the method includes the following content.

400. A radio access network determines configuration information of aduplication mode.

The configuration information may be a configuration of the duplicationmode of a radio bearer on the uplink or the downlink.

401. A terminal device receives the configuration information sent bythe radio access network.

Optionally, the configuration information indicates a cell or a cellgroup corresponding to a first path and a cell or a cell groupcorresponding to a second path. Optionally, for the uplink, the terminaldevice may send, based on the configuration information, data on thefirst path to the radio access network through the cell or the cellgroup corresponding to the first path or data on the second path to theradio access network through the cell or the cell group corresponding tothe second path.

Optionally, for the downlink, based on the configuration information,the terminal device receives, from the cell or the cell groupcorresponding to the first path, data sent by the radio access networkthrough the cell or the cell group corresponding to the first path, orreceives, from the cell or the cell group corresponding to the secondpath, data sent by the radio access network through the cell or the cellgroup corresponding to the second path. The cell or the cell groupcorresponding to the first path and the cell or the cell groupcorresponding to the second path may belong to one DU, and theconfiguration information may be generated by the one DU and sent by theDU to the terminal device, or generated by a CU corresponding to the DUand sent to the terminal device through the DU. The cell or the cellgroup corresponding to the first path and the cell or the cell groupcorresponding to the second path may alternatively belong to differentDUs.

Optionally, in a scenario in which the CU generates the configurationinformation of the duplication mode, the CU sends the configurationinformation of the duplication mode to the DU through an F1 interface.Optionally, the configuration information further includes aconfiguration of an identifier of at least one radio bearer in theduplication mode, a configuration of a PDCP entity in each radio bearer,configurations of at least two RLC entities corresponding to the PDCPentity (for example, identifiers of the RLC entities or identifiers ofpaths), cells or cell groups corresponding to the paths on which the RLCentities are located, an identifier of a session to which data on eachradio bearer belongs, a quality of service flow identifier correspondingto each radio bearer, a quality of service parameter, and the like.After the duplication mode is activated, the DU schedules the data basedon the cells or the cell groups corresponding to the paths on which theRLC entities are located. For example, an RLC entity 1 and an RLC entity2 corresponding to a radio bearer correspond to a cell group 1 and acell group 2, respectively. In this case, when receiving data on the RLCentity 1 corresponding to the radio bearer, the DU schedules the data onthe RLC entity 1 to a cell in the cell group 1 for transmission; or whenreceiving data from the RLC entity 2, the DU schedules the data on theRLC entity 2 to a cell in the cell group 2 for transmission.

Optionally, when the CU and the DU establish a tunnel for each radiobearer of the terminal device through the F1 interface, the CU adds theconfiguration information of the duplication mode to configurationinformation of each radio bearer. For example, the CU provides anidentifier of the radio bearer, the configuration information of theduplication mode, and a tunnel address of the radio bearer in the CU. Inanother possible implementation, for a control plane, the CU sends, tothe DU through the F1 interface, an RRC message including theconfiguration information of the duplication mode, so that the DU canforward the RRC message to the UE. The DU may parse the RRC message toobtain the configuration information of the duplication mode.Particularly, if the RRC message does not include the cells or the cellgroups corresponding to the paths on which the RLC entities are located,the CU notifies, via another message, the DU of the cells or the cellgroups corresponding to the paths on which the RLC entities are located.

Optionally, the cells or the cell groups corresponding to the paths onwhich the RLC entities are located and RLC/MAC/PHY layer configurationinformation of the radio bearer are determined by the DU. The DUnotifies, through the F1 interface, the CU of the cells or the cellgroups corresponding to the paths on which the at least two RLC entitiescorresponding to the radio bearer are located and the RLC/MAC/PHY layerconfiguration information of the radio bearer, so that the CU adds theinformation to the RRC message and notifies the UE.

In step 401, the terminal device may receive the configurationinformation in a process of accessing the radio access network. Forexample, the terminal device establishes an RRC connected mode, forexample, performs initial access, handover, and radio linkreestablishment, when accessing the radio access network.

In step 401, the configuration information may be carried in an RRCmessage. The configuration information may further indicateconfigurations of a first RLC entity and a second RLC entity thatcorrespond to one PDCP entity in one radio bearer in the duplicationmode. For example, different identifiers are configured for the two RLCentities (in other words, the first path and the second path). Thedifferent identifiers may be different logical channel identifiers ornewly defined different identifiers.

Optionally, during transmission on the uplink, the configurationinformation may further indicate which of the first RLC entity and thesecond RLC entity is allowed to be used by the terminal to transmit datawhen the duplication mode is deactivated. This implementation may beused in a single-radio access device carrier aggregation or dualconnectivity scenario.

Optionally, the configuration information of the duplication mode may begenerated by the CU and sent to the terminal device via the RRC message.Because no RRC layer on the DU corresponds to that on the CU, the DUdoes not parse the RRC message, but directly forwards the RRC message tothe terminal device. Further, the CU adds the configuration informationof the duplication mode to a CU-DU interface message that can be parsedby the DU, and sends the CU-DU interface message to the DU, so that theDU completes configuration of the duplication mode.

Optionally, in the dual connectivity scenario, the configurationinformation may indicate that when the duplication mode is deactivated,non-duplicated data is sent between the terminal device and at least oneof a primary radio access device and a secondary radio access device. Ina possible implementation, the terminal device may be configured to senddata or a data volume report on a path on which at least one of theprimary radio access device and the secondary radio access device islocated, and a data volume threshold may be further configured for theterminal device. If a to-be-sent data volume of the terminal deviceexceeds the data volume threshold, the terminal device sends data to theprimary radio access device and the secondary radio access device,thereby implementing split transmission of non-duplicated data; or if ato-be-sent data volume of the terminal device does not exceed the datavolume threshold, the terminal device sends data to the configured oneof the primary radio access device and the secondary radio accessdevice. In this possible implementation, because data is always beingsent at RLC layers, the radio access network and the terminal device donot know whether a data transmission mode changes, and implementation issimple; or the terminal device and the radio access network maintainsame RLC numbering records at RLC layers, so that when the duplicationmode is activated, numbers of same data transmitted between the terminaldevice and the radio access network are still the same.

Optionally, regardless of the uplink or the downlink, if theconfiguration information indicates a primary cell or a master cellgroup corresponding to the first path, the first path is activated bydefault to send non-duplicated data; or if the configuration informationindicates a secondary cell or a secondary cell group corresponding tothe second path, the second path is disabled by default, or isprohibited from sending duplicated data but can send non-duplicateddata. In this case, the duplication mode is deactivated. On the uplink,the terminal device sends non-duplicated data on the first path and thesecond path. On the downlink, the terminal device receives, on the firstpath and the second path, non-duplicated data sent by the radio accessnetwork.

Optionally, regardless of the uplink or the downlink, if theconfiguration information indicates a primary cell or a master cellgroup corresponding to the first path, the first path is activated bydefault to send duplicated data; or if the configuration informationindicates a secondary cell or a secondary cell group corresponding tothe second path, the second path is activated by default to sendduplicated data. In this case, the duplication mode is activated. On theuplink, the terminal device sends duplicated data on the first path andthe second path. On the downlink, the terminal device receives, on thefirst path and the second path, duplicated data sent by the radio accessnetwork.

Optionally, in the dual connectivity scenario, a radio access devicethat sends a first indication message is determined through negotiationbetween the primary radio access device and the secondary radio accessdevice, and the radio access device that sends the first indicationmessage is notified to the terminal device in the configurationinformation. If the terminal device receives a first indication messagesent by a radio access device that is not notified, the terminal ignoresthe first indication message sent by the radio access device.

Optionally, in the dual connectivity scenario, the configurationinformation indicates that the terminal device determines, based on thefirst indication message sent by the primary radio access device,whether a radio bearer of the primary radio access device is activated,and ignores a first indication message sent by the secondary radioaccess device.

Optionally, in the dual connectivity scenario, the configurationinformation indicates that the terminal device determines, based on thefirst indication message sent by the secondary radio access device,whether a radio bearer of the secondary radio access device isactivated, and ignores a first indication message sent by the primaryradio access device.

Optionally, in the dual connectivity scenario, if the primary radioaccess device duplicates data transmitted on the secondary radio accessdevice, the terminal device determines, based on the first indicationmessage sent by the secondary radio access device, whether a radiobearer is activated, and ignores a first indication message sent by theprimary radio access device. If the secondary radio access device splitsdata transmitted on the primary radio access device, the terminal devicedetermines, based on the first indication message sent by the primaryradio access device, whether a radio bearer is activated, and ignores afirst indication message sent by the secondary radio access device.

Optionally, the configuration information indicates whether a type ofthe radio bearer is the duplication mode.

Optionally, the configuration information indicates, specificallythrough presence or absence of an information element, whether a type ofa radio bearer is a duplication mode. If the configuration informationincludes the information element, the type of the radio bearer is theduplication mode; otherwise, the type of the radio bearer is not theduplication mode. Optionally, if the configuration information includesthe information element indicating that the radio bearer is a radiobearer in the duplication mode, the configuration information furtherindicates whether the duplication mode is activated.

Optionally, in the dual connectivity scenario, the configurationinformation may specifically indicate a data transmission path of aradio bearer, to indicate whether the radio bearer is in the duplicationmode. When the data transmission path indicated in the configurationinformation is one of a path on which the primary radio access device islocated and a path on which the secondary radio access device islocated, the radio bearer is not in the duplication mode, or that theduplication mode is deactivated. When the data transmission pathindicated in the configuration information is a path on which theprimary radio access device is located and a path on which the secondaryradio access device is located, the type of the radio bearer is theduplication mode.

According to the technical solution provided in the third embodiment,the radio access network may configure configuration information of aduplication mode on at least one of the downlink and the uplink for theterminal device, so as to implement configuration management of theduplication mode on at least one of the downlink and the uplink.

A fourth embodiment of this application provides a communicationprocessing method, and relates to how to number duplicated data on atleast two RLC entities (for example, a first RLC entity and a second RLCentity) corresponding to one PDCP entity on an uplink or a downlink in aduplication mode, so as to complete a communication processing procedureat an RLC layer. The fourth embodiment may be based on the architecture,of the protocol stack of the wireless communications system, shown inany one of FIG. 1A, FIG. 1B to FIG. 1F, and FIG. 1G and FIG. 1H. On theuplink, a transmit end may be a terminal device, and a receive end is aradio access network; or on the downlink, a transmit end is a radioaccess network, and a receive end is a terminal device. The fourthembodiment may be independent of the foregoing embodiments, or may beused as a further processing procedure of the first embodiment to thethird embodiment at the RLC layer.

When the duplication mode is activated, duplicated data on the first RLCentity and the second RLC entity has a same number or different numbers.

When the duplicated data has the same number, the transmit end sends asecond indication message to the receive end, where the secondindication message indicates a start number of the duplicated data onthe second RLC entity in the duplication mode. In this case, the receiveend may determine, based on the start number of the duplicated data onthe second RLC entity, which duplicated data from the transmit end hasbeen received. If duplicated data on one of a first path and a secondpath has been received by the receive end, even if the duplicated dataon the other path has not been received, the receive end indicates, inan RLC layer status report, that the duplicated data has been received,and does not instruct the other path to retransmit the duplicated data.In this case, the receive end sends only one RLC status report to thetransmit end, and does not need to generate an RLC status report foreach of the two RLC entities.

Optionally, when the duplicated data has different numbers, the transmitend notifies the receive end of a difference between the differentnumbers of the duplicated data on the first RLC entity and the secondRLC entity.

Optionally, when receiving an RLC status report of one of the first RLCentity and the second RLC entity, the receive end may determine a numberof the duplicated data on the other RLC entity based on the difference.Optionally, the receive end considers by default that a start number ofthe duplicated data on the second RLC entity starts from a defaultinteger (for example, 0). The receive end may calculate a number of theduplicated data on the second RLC entity based on the difference and anumber of the duplicated data in an RLC status report of the first RLCentity. When the duplication mode switches from an activated state to adeactivated state, the start number of the duplicated data on the secondRLC entity is reset to the default integer (for example, 0).

Optionally, when the duplicated data has the different numbers, an RLCstatus report is generated for each of the first RLC entity and thesecond RLC entity corresponding to the one PDCP entity at the receiveend. The receive end may convert a number of the duplicated data on thefirst RLC entity into a number of the duplicated data on the second RLCentity based on the difference between the different numbers of theduplicated data, and send the number of the duplicated data on thesecond RLC entity to the second RLC entity at the receive end via an RLCstatus report of the second RLC entity. Alternatively, the receive endmay convert a number of the duplicated data on the second RLC entityinto a number of the duplicated data on the first RLC entity based onthe difference between the different numbers of the duplicated data, andsend the number of the duplicated data on the first RLC entity to thefirst RLC entity at the receive end via an RLC status report of thefirst RLC entity.

Optionally, when the duplicated data has the different numbers, thereceive end converts a number of the duplicated data on one of the firstRLC entity and the second RLC entity into a number of the duplicateddata on the other RLC entity based on the difference between thedifferent numbers of the duplicated data, adds the number of theduplicated data on the other RLC entity to an RLC status reportcorresponding to the other RLC entity, and sends the RLC status reportto the transmit end.

Optionally, when the duplication mode is deactivated, a number ofduplicated data on the second RLC entity at the transmit end is set to0, or the transmit end stores a value of the last number receivedcurrently.

Optionally, for data transmission on the uplink, the terminal devicedetermines, based on a deviation between transmission rates of datapackets on two paths (for example, by detecting a deviation between RLCnumbers of data packets arriving at two RLC entities at the same time),whether to deactivate the duplication mode.

In this case, optionally, if the deviation between the transmissionrates of the data packets on the two paths is greater than a threshold,the terminal may automatically trigger deactivation of the duplicationmode.

In this case, optionally, if a deviation between numbers of same PDCPdata packets on the two paths is greater than a threshold (for example,0), the PDCP entity may notify the deviation to an RLC entity on a pathcorresponding to a PDCP data packet having a smaller number in the samePDCP data packets, so that the RLC entity on the path adds an RLCreceive status variable and the derivation, to avoid the followingproblem: A path with a lower transmission rate frequently sends an RLCstatus report to notify the terminal device of data packets that havenot been received, and if retransmission fails, an unnecessary radiolink failure may be caused.

In this case, optionally, if the deviation between the transmissionrates of the data packets on the two paths is greater than a threshold,the PDCP entity in the radio access network may notify an RLC entity ona path with a lower transmission rate of a number of a PDCP data packetreceived on a path with a higher transmission rate, so that the RLCentity on the path with the lower transmission rate determines, based ona number of a PDCP data packet corresponding to a received RLC datapacket and the notified number of the PDCP data packet, a step by whichan RLC receiving window on the path with the lower transmission ratemoves to an RLC receiving window on the path with the highertransmission rate. For example, the RLC receiving window on the pathwith the lower transmission rate and the RLC receiving window on thepath with the higher transmission rate keep the same as each other viathe step.

In a CU-DU networking architecture, because the PDCP entity is locatedon a CU, and the RLC entities are located on a DU, the foregoing varioustypes of information sent by the PDCP entity to the RLC entities aresent by the CU to the DU in physical implementation.

Optionally, in a dual connectivity scenario, for data transmission onthe downlink, if detecting that a derivation between numbers of PDCPdata packets received on two paths reaches a preset threshold, theterminal device instructs the radio access network (for example, aprimary radio access device or a secondary radio access device) to senda report, where the report indicates that the derivation between thenumbers of the PDCP data packets reaches the preset threshold, so thatthe radio access network determines whether to deactivate theduplication mode.

According to the technical solution provided in the fourth embodiment ofthis application, the transmit end can number the duplicated data in theduplication mode, so that the receive end can learn whether theduplicated data on the two paths has been received.

A fifth embodiment of this application provides a terminal device. Asshown in FIG. 14, the terminal device includes a processing unit 1401and a sending unit 1402.

The processing unit 1401 is configured to determine that a data volumereport needs to be triggered for one of a first path and a second paththat are in a radio bearer in a duplication mode, where in theduplication mode, PDCP data on the radio bearer is transmitted on acorresponding first RLC entity on the first path, and is duplicatelytransmitted on a corresponding second RLC entity on the second path.

The processing unit 1401 is further configured to trigger the datavolume report, where the data volume report indicates a data volume onthe one path.

The sending unit 1402 is configured to send the data volume report to aradio access network.

The processing unit 1401 is configured to perform processing actionssuch as determining and triggering that are performed by the terminaldevice in the foregoing communication processing method embodiments, andthe sending unit 1402 is configured to perform sending actions in theforegoing communication processing method embodiments. Optionally, theterminal device further includes a receiving unit 1403 (not shown inFIG. 14), configured to perform receiving actions of the terminal devicein the foregoing communication processing method embodiments.Optionally, the communications apparatus is the terminal device or apart of the terminal device. Optionally, the processing unit 1401 may bea processor of the terminal device, the sending unit 1402 may be atransmitter of the terminal device, and the receiving unit 1403 is areceiver of the terminal device. Further, the terminal device mayfurther include another electronic line, for example, a bus connectingthe processor and the transmitter, and a radio frequency antenna usedfor sending a signal. Optionally, the communications apparatus mayalternatively be a chip.

A sixth embodiment of this application provides a communicationsapparatus. As shown in FIG. 15, the communications apparatus includes aprocessing unit 1501 and a receiving unit 1502.

The receiving unit 1502 is configured to receive a first indicationmessage sent by a radio access network, where the first indicationmessage indicates whether to activate a duplication mode of a radiobearer, and in the duplication mode, PDCP data on the radio bearer istransmitted on a corresponding first RLC entity on a first path, and isduplicately transmitted on a corresponding second RLC entity on a secondpath.

The processing unit 1501 is configured to activate or deactivate theduplication mode of the radio bearer based on the first indicationmessage.

The processing unit 1501 is configured to perform processing actionssuch as determining and triggering that are performed by the terminaldevice in the foregoing communication processing method embodiments, andthe receiving unit 1502 is configured to perform receiving actions ofthe terminal device in the foregoing communication processing methodembodiments. The communications apparatus may further include a sendingunit 1503 (not shown in FIG. 15), configured to perform sending actionsin the foregoing communication processing method embodiments.Optionally, the communications apparatus is the terminal device or apart of the terminal device. Optionally, the processing unit 1501 may bea processor of the terminal device, the sending unit 1503 may be atransmitter of the terminal device, and the receiving unit 1502 is areceiver of the terminal device. Further, the terminal device mayfurther include another electronic line, for example, a bus connectingthe processor and the transmitter, and a radio frequency antenna usedfor sending a signal. Optionally, the communications apparatus mayalternatively be a chip. The technical solution provided in the fourthaspect has the technical effects of the foregoing correspondingimplementations. For details, refer to the foregoing implementations.

An embodiment of this application further provides a schematicstructural diagram of a terminal device 1600 shown in FIG. 16. Astructure of the terminal 1600 may be used as a general structure of theterminal device in the foregoing embodiments. The terminal 1600 includescomponents such as a radio frequency (RF) circuit 1610, a memory 1620,an input unit 1630, a display unit 1640, a sensor 1650, an audio circuit1660, a wireless fidelity (Wi-Fi) module 1670, a processor 1680, and apower supply 1690.

The RF circuit 1610 may be configured to receive and send information,or receive and send a signal during a call. For example, after receivingdata from a radio access device, the RF circuit 1610 sends the data tothe processor 1680 for processing, and sends the data to a base station.Usually, the RF circuit includes but is not limited to an antenna, atleast one amplifier, a transceiver, a coupler, a low noise amplifier(LNA), a duplexer, and the like.

The memory 1620 may be configured to store a software program and amodule, and the processor 1680 executes various functional applicationsand data processing of the terminal 1600 by running the software programand the module that are stored in the memory 1620. The memory 1620 maymainly include a program storage area and a data storage area. Theprogram storage area may store an operating system, an applicationprogram required for at least one function (such as a voice playbackfunction and an image display function), and the like; and the datastorage area may store data (such as audio data and a phone book)created based on use of the terminal 1600, and the like. In addition,the memory 1620 may include a high speed random access memory, and mayfurther include a nonvolatile memory, such as at least one magnetic diskstorage device, a flash storage device, or another volatile solid-statestorage device.

The input unit 1630 may be configured to: receive input digit orcharacter information and generate key signal input related to usersetting and function control of the terminal 1600. Specifically, theinput unit 1630 may include a touch panel 1631 and another input device1632. The touch panel 1631, also referred to as a touchscreen, maycollect a touch operation performed by a user on or near the touch panel(for example, an operation performed by the user on or near the touchpanel 1631 via any suitable object or accessory such as a finger or astylus), and drive a corresponding connection apparatus according to apreset program. Optionally, the touch panel 1631 may include two parts:a touch detection apparatus and a touch controller. The touch detectionapparatus detects a location touched by the user, detects a signalbrought by a touch operation, and transmits the signal to the touchcontroller. The touch controller receives touch information from thetouch detection apparatus, converts the touch information into touchpoint coordinates, and sends the touch point coordinates to theprocessor 1680, and can receive and execute a command sent by theprocessor 1680. In addition, the touch panel 1631 may be implemented ina plurality of types, such as a resistive type, a capacitive type, aninfrared type, and a surface acoustic wave type. The input unit 1630 mayinclude the another input device 1632 in addition to the touch panel1631. Specifically, the another input device 1632 may include but is notlimited to one or more of a physical keyboard, a function key (such as avolume control key or a switch key), a trackball, a mouse, a joystick,and the like.

The display unit 1640 may be configured to display information enteredby the user or information provided for the user, and various menus ofthe terminal 1600. The display unit 1640 may include a display panel1641. Optionally, the display panel 1641 may be configured in a form ofa liquid crystal display (LCD), an organic light-emitting diode (OLED),or the like. Further, the touch panel 1631 may cover the display panel1641. When detecting a touch operation on or near the touch panel 1631,the touch panel 1631 transmits information about the touch operation tothe processor 1680 to determine a type of a touch event, and then theprocessor 1680 provides corresponding visual output on the display panel1641 based on the type of the touch event. Although the touch panel 1631and the display panel 1641 in FIG. 16 are used as two independent partsto implement input and output functions of the terminal 1600, in someembodiments, the touch panel 1631 and the display panel 1641 may beintegrated to implement the input and output functions of the terminal1600.

The terminal 1600 may further include at least one sensor 1650 such as alight sensor, a motion sensor, and another sensor. Specifically, thelight sensor may include an ambient light sensor and a proximity sensor.The ambient light sensor may adjust luminance of the display panel 1641based on brightness of ambient light. The light sensor may turn off thedisplay panel 1641 and/or backlight when the terminal 1600 moves to anear. As a type of motion sensor, an acceleration sensor may detectvalues of acceleration in directions (usually three axes), may detect,in a static state, a value and a direction of gravity, and may be usedfor an application that identifies a posture (such as screen switchingbetween a landscape mode and a portrait mode, a related game, andmagnetometer posture calibration) of the terminal, avibration-identification-related function (such as a pedometer andtapping), and the like. Other sensors that can be configured for theterminal 1600, such as a gyroscope, a barometer, a hygrometer, athermometer, and an infrared sensor, are not described herein.

The audio circuit 1660, a speaker 1661, and a microphone 1662 mayprovide audio interfaces between the user and the terminal 1600. Theaudio circuit 1660 may transmit, to the speaker 1661, an electricalsignal that is obtained through conversion of received audio data, andthe speaker 1661 converts the electrical signal into an audio signal andoutputs the audio signal. In addition, the microphone 1662 converts acollected audio signal into an electrical signal, the audio circuit 1660receives the electrical signal, converts the electrical signal intoaudio data, and outputs the audio data to the processor 1680 forprocessing, and then processed audio data is sent to, for example,another terminal, via the RF circuit 1610, or the audio data is outputto the memory 1620 for further processing.

Wi-Fi is a short-distance wireless transmission technology. Via theWi-Fi module 1670, the terminal 1600 can help the user receive and sendan email, browse a web page, access streaming media, and the like. TheWi-Fi module 1670 provides wireless broadband Internet access for theuser. Although FIG. 16 shows the Wi-Fi module 1670, it can be understoodthat the Wi-Fi module 1670 is not a mandatory constituent part of theterminal 1600, and may be totally omitted depending on requirementswithout changing the essence of this application.

The processor 1680 is a control center of the terminal 1600, and isconnected to various parts of the entire terminal 1600 via variousinterfaces and lines. By running or executing the software programand/or the module stored in the memory 1620, and invoking data stored inthe memory 1620, the processor 1680 performs various functions of theterminal 1600 and processes data, thereby performing overall monitoringon the terminal 1600. Optionally, the processor 1680 may include one ormore processing units. For example, an application processor and a modemprocessor may be integrated into the processor 1680. The applicationprocessor mainly processes an operating system, a user interface, anapplication program, and the like; and the modem processor mainlyprocesses wireless communication. It may be understood that theforegoing modem processor may alternatively not be integrated into theprocessor 1680.

The terminal 1600 further includes the power supply 1690 (for example, abattery) that supplies power to the components. Optionally, the powersupply may be logically connected to the processor 1680 via a powermanagement system. In this way, functions such as management ofcharging, discharging, and power consumption are implemented via thepower management system.

The terminal 1600 may further include a camera 1700. The camera may be afront-facing camera, or may be a rear-facing camera. Although not shown,the terminal 1600 may further include a Bluetooth module, a globalpositioning system (GPS) module, and the like. Details are not describedherein.

In this application, the processor 1680 included in the terminal 1600may be configured to perform the foregoing communication processingmethod embodiments, and implementation principles and technical effectsthereof are similar to those of the foregoing communication processingmethod embodiments. Details are not described herein again.

An embodiment of this application further provides a communicationsapparatus, including a processor and a memory. The memory stores code,and when the code is invoked by the processor, actions of the methodperformed by the terminal device in the foregoing communicationprocessing method embodiments are implemented. The communicationsapparatus may be the terminal device, or the communications apparatusmay be a chip. The chip includes a processor including at least one gatecircuit and a memory including at least one gate circuit, each gatecircuit includes at least one transistor (for example, a field effecttransistor) connected through a conducting wire, and each transistor ismade of a semiconductor material. The chip may be a central processingunit (CPU), or may be a field programmable gate array (FPGA) or adigital signal processor (DSP).

Persons skilled in the art should understand that the embodiments of thepresent application may be provided as a method, a system, or a computerprogram product. Therefore, the present application may use a form ofhardware only embodiments, software only embodiments, or embodimentswith a combination of software and hardware. Moreover, the presentapplication may use a form of a computer program product that isimplemented on one or more chip systems or computer-usable storage media(including but not limited to a magnetic disk memory, a CD-ROM, anoptical memory, and the like) that include computer-usable program code.

The present application is described with reference to the flowchartsand/or block diagrams of the method, the apparatus (system), and thecomputer program product according to the embodiments of the presentapplication. It should be understood that computer program instructionsmay be used to implement each process and/or each block in theflowcharts and/or the block diagrams, and a combination of a processand/or a block in the flowcharts and/or the block diagrams. Thesecomputer program instructions may be provided for a general-purposecomputer, a special-purpose computer, an embedded processor, or aprocessor of another programmable data processing device to generate amachine, so that the instructions executed by the computer or theprocessor of another programmable data processing device generate anapparatus for implementing a specified function in one or more processesin the flowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may be alternatively stored in acomputer readable memory that can instruct a computer or anotherprogrammable data processing device to work in a specific manner, sothat the instructions stored in the computer readable memory generate anartifact that includes an instruction apparatus. The instructionapparatus implements a specified function in one or more processes inthe flowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may be alternatively loaded onto acomputer or another programmable data processing device, so that aseries of operation steps are performed on the computer or the anotherprogrammable device, thereby generating computer-implemented processing.Therefore, the instructions executed on the computer or the anotherprogrammable device provide steps for implementing a specified functionin one or more processes in the flowcharts and/or in one or more blocksin the block diagrams.

Although some embodiments of the present application have beendescribed, persons skilled in the art can make changes and modificationsto these embodiments once they learn of the basic inventive concept.Therefore, the appended claims are intended to be construed as coveringthe preferred embodiments and all changes and modifications fallingwithin the scope of the present application.

Apparently, persons skilled in the art can make various modificationsand variations to the present application without departing from thescope of the present application. The present application is intended tocover these modifications and variations to the present applicationprovided that they fall within the scope of the claims of the presentapplication and equivalent technologies thereof.

1. A communication processing method, comprising: determining, by aradio access device, whether to activate a duplication mode of a radiobearer, wherein the duplication mode of the radio bearer is configuredwith a packet data convergence protocol (PDCP) entity in the radiobearer, wherein a first radio link control (RLC) entity corresponds tothe PDCP entity and a second RLC entity corresponds to the PDCP entity;sending, by the radio access device to a terminal device, a firstindication message indicating to activate or deactivate the duplicationmode of the radio bearer; wherein the first indication message comprisesa first field and a second field, wherein the first field indicates thatthe first indication message is a control message for the duplicationmode; and wherein a first logical channel corresponding to the first RLCentity is activated and the second field indicates whether a secondlogical channel corresponding to the second RLC entity is activated,wherein the duplication mode of the radio bearer is activated when thesecond logical channel is activated.
 2. The method according to claim 1,wherein the duplication of the radio bearer is configured with multipleRLC entities corresponding to multiple second logical channels, and themultiple second logical channels comprise the second logical channelcorresponding to the second RLC entity; and wherein the second fieldcomprises multiple bits corresponding to the multiple second logicalchannels, wherein each bit of the multiple bits indicates acorresponding second logical channel via a position of the bit andindicates, via a bit state of the bit, whether the corresponding secondlogical channel is activated.
 3. The method according to claim 1,wherein the duplication mode is deactivated, the first RLC entity is aprimary RLC entity, and the method further comprises: receiving, by theradio access device on the PDCP entity, data from the first RLC entityand determining not to receive duplicated data of data from the secondRLC entity; or receiving, by the radio access device on the PDCP entity,data from the first RLC entity and receiving non-duplicated data of datafrom the second RLC entity.
 4. The method according to claim 1, whereinthe radio bearer is a data radio bearer (DRB).
 5. A communicationprocessing method, comprising: receiving, by a terminal device from aradio access device, a first indication message indicating to activateor deactivate a duplication mode of a radio bearer, wherein theduplication mode of the radio bearer is configured with a packet dataconvergence protocol (PDCP) entity in the radio bearer, wherein a firstradio link control (RLC) entity corresponds to the PDCP entity and asecond RLC entity corresponds to the PDCP entity; and activating ordeactivating, by the terminal device, the duplication mode of the radiobearer based on the first indication message, wherein the firstindication message comprises a first field and a second field, whereinthe first field indicates that the first indication message is a controlmessage for the duplication mode; and wherein a first logical channelcorresponding to the first RLC entity is activated and the second fieldindicates whether a second logical channel corresponding to the secondRLC entity is activated, wherein the duplication mode of the radiobearer is activated when the second logical channel is activated.
 6. Themethod according to claim 5, wherein the duplication of the radio beareris configured with multiple RLC entities corresponding to multiplesecond logical channels, and the multiple second logical channelscomprise the second logical channel corresponding to the second RLCentity; and wherein the second field comprises multiple bitscorresponding to the multiple second logical channels, wherein each bitof the multiple bits indicates a corresponding second logical channelvia a position of the bit and indicates, via a bit state of the bit,whether the corresponding second logical channel is activated.
 7. Themethod according to claim 5, wherein the duplication mode isdeactivated, the first RLC entity is a primary RLC entity, and themethod further comprises: transmitting, by the terminal device, datafrom the PDCP entity to the first RLC entity and determining not totransmit duplicated data of data from PDCP entity to the second RLCentity; or transmitting, by the terminal device, data from the PDCPentity to the first RLC entity and transmitting non-duplicated data ofdata from the PDCP entity to the second RLC entity.
 8. The methodaccording to claim 5, wherein the radio bearer is a data radio bearer(DRB).
 9. The method according to claim 5, where the method furthercomprises: in response to a quantity of retransmission times ofduplicated data on the second RLC entity reaching a maximum quantity ofRLC retransmission times, triggering, by the terminal device, a radiolink failure of a radio link without reestablishing the radio link. 10.The method according to claim 5, wherein the method further comprises:in response to a quantity of retransmission times of duplicated data onthe second RLC entity reaching a maximum quantity of RLC retransmissiontimes, determining, by the terminal device, a radio link failure is nottriggered.
 11. The method according to claim 5, wherein the firstindication message indicates that the duplication mode is deactivated,and the method further comprises: discarding, by the terminal device,duplicated data on the second RLC entity.
 12. The method according toclaim 5, wherein the first indication message indicates that theduplication mode is deactivated, and the method further comprises:determining, by the terminal device, duplicated data on the second RLCentity that does not need to be transmitted through an air interface;and continuing to transmit, by the terminal device, the determinedduplicated data on the second RLC entity in response to the determinedduplicated data on the second RLC entity has started being transmittedthrough the air interface.
 13. A radio access device, comprising: aprocessor; and a memory storing instructions, wherein the instructionsare executed by the processor to cause the radio access device toperform operations of: determining whether to activate a duplicationmode of a radio bearer, wherein the duplication mode of the radio beareris configured with a packet data convergence protocol (PDCP) entity inthe radio bearer, wherein a first radio link control (RLC) entitycorresponds to the PDCP entity and a second RLC entity corresponds tothe PDCP entity; and sending to a terminal device, a first indicationmessage indicating to activate or deactivate the duplication mode of theradio bearer, wherein the first indication message comprises a firstfield and a second field, wherein the first field indicates that thefirst indication message is a control message for the duplication mode;and wherein a first logical channel corresponding to the first RLCentity is activated and the second field indicates whether a secondlogical channel corresponding to the second RLC entity is activated,wherein the duplication mode of the radio bearer is activated when thesecond logical channel is activated.
 14. The radio access deviceaccording to claim 13, wherein the duplication of the radio bearer isconfigured with multiple RLC entities corresponding to multiple secondlogical channels, and the multiple second logical channels comprise thesecond logical channel corresponding to the second RLC entity; andwherein the second field comprises multiple bits corresponding to themultiple second logical channels, wherein each bit of the multiple bitsindicates a corresponding second logical channel via a position of thebit and indicates, via a bit state of the bit, whether the correspondingsecond logical channel is activated.
 15. The radio access deviceaccording to claim 13, wherein the duplication mode is deactivated, thefirst RLC entity is a primary RLC entity, and the operations furthercomprise: receiving on the PDCP entity, data from the first RLC entityand determining not to receive duplicated data of data from the secondRLC entity; or receiving on the PDCP entity, data from the first RLCentity and receiving non-duplicated data of data from the second RLCentity.
 16. A terminal device, comprising: a processor; and a memorystoring instructions wherein the instructions are executed by theprocessor to cause the terminal device to perform operations of:receiving from a radio access device, a first indication messageindicating to activate or deactivate a duplication mode of a radiobearer, wherein the duplication mode of the radio bearer is configuredwith a packet data convergence protocol (PDCP) entity in the radiobearer, wherein a first radio link control (RLC) entity corresponds tothe PDCP entity and a second RLC entity corresponds to the PDCP entity;and activating or deactivating the duplication mode of the radio bearerbased on the first indication message, wherein the first indicationmessage comprises a first field and a second field, wherein the firstfield indicates that the first indication message is a control messagefor the duplication mode; and wherein a first logical channelcorresponding to the first RLC entity is always activated and the secondfield indicates whether a second logical channel corresponding to thesecond RLC entity is activated, wherein the duplication mode of theradio bearer is activated when the second logical channel is activated.17. The terminal device according to claim 16, wherein the duplicationof the radio bearer is configured with multiple RLC entitiescorresponding to multiple second logical channels, and the multiplesecond logical channels comprise the second logical channelcorresponding to the second RLC entity; and wherein the second fieldcomprises multiple bits corresponding to the multiple second logicalchannels, wherein each bit of the multiple bits indicates acorresponding second logical channel via a position of the bit andindicates, via a bit state of the bit, whether the corresponding secondlogical channel is activated.
 18. The terminal device according to claim16, wherein the duplication mode is deactivated, the first RLC entity isa primary RLC entity, and the operations further comprise: transmittingdata from the PDCP entity to the first RLC entity and determining not totransmit duplicated data of data from PDCP entity to the second RLCentity; or transmitting data from the PDCP entity to the first RLCentity and transmitting non-duplicated data of data from the PDCP entityto the second RLC entity.
 19. The terminal device according to claim 16,wherein the operations further comprise: in response to a quantity ofretransmission times of duplicated data on the second RLC entityreaching a maximum quantity of RLC retransmission times, triggering aradio link failure of a radio link without reestablishing the radiolink.
 20. The terminal device according to claim 16, wherein theoperations further comprise: in response to a quantity of retransmissiontimes of duplicated data on the second RLC entity reaching a maximumquantity of RLC retransmission times, determining a radio link failureis not triggered.
 21. The terminal device according to claim 16, whereinthe first indication message indicates that the duplication mode isdeactivated, and the operations further comprise: discarding duplicateddata on the second RLC entity.
 22. The terminal device according toclaim 16, wherein the first indication message indicates that theduplication mode is deactivated, and the operations further comprises:determining duplicated data on the second RLC entity that does not needto be transmitted through an air interface; and continuing to transmitthe determined duplicated data on the second RLC entity in response tothe determined duplicated data on the second RLC entity has startedbeing transmitted through the air interface.